Related
Kernel Update Utility 0.9YouTube video"Making kernel flashing a bit easier"
About:
This lightweight tool takes a kernel, and flashes it to your device. You can give it the kernel in zImage or CWM flashable zip format. Some people have come across bootloops when using clockworkmod to flash kernels, hopefully this tool will prove to fit better for the job. It can also push and apply kernel modules. I have now flashed a kernel using this tool more times than I can count, and not a single bootloop or failed flash.
This tool is ideal for people who do not want to mess with command lines, and people who want the job done fast and easy.
System requirements:
Windows XP SP2 or higher
.NET 4.0
HTC Sync (or ADB drivers)
Rooted, ENG S-OFF Desire HD
Changelog:
0.9:
- Added support for Lee's kernels
0.8:
- Added support for Kamma's new kernels
0.7:
- Fixed Windows XP file not found -bug
- Optimized the code further
0.6:
- Most cmd windows hidden
- Better instructions in module pushing
- Out of beta!
0.5a:
- Optimized a lot of code
- Improved SU permissions; fixed modules not getting pushed with phones that do not have root adb by default
- Cleans up /system/lib/modules to ensure cp functionality
0.4:
- It is now possible to choose multiple modules
- It cleans up afterwards
0.3:
- CWM zip file flashing, pushes all modules
- Space in filename -bug fixed
0.2:
- Initial release
Click to expand...
Click to collapse
If you like my work, please consider (or just hit the thanks button ):
Hi,
thanks !!
Please add more selections for ko files:
- tun.ko
- cifs.ko
- other
with friendly greet
starbase64
Yeah, I will
I will also make this work with CWM flashable zips, I am programming that in right now.
Hi,
good news, thanks.
with friendly greet
starbase64
It can now flash zip files that would usually be flashed in clockworkmod. Using my app to flash it should reduce the possibility of a bootloop. Also the space in filename -bug has been fixed.
e: Another update, now for selecting and applying kernel modules. Please leave feedback! Is there something I should change? Any features you would like to see in this tool?
Keep in mind that this tool can also be used for recovering from some bootloops, where kernel itself is not properly flashed. In some situations, however, boot.img corrupts in CWM flash, then you will have to restore a partial nandroid.
thanks.. now i wish there is a tool for pushing ENG hboot and CWM recovery .. where is unrevoked
Well, I can enable my tool to flash a recovery, but because flashing hboot is so risky, I think I will not do that feature..
So, are people interested in a recovery flasher?
So now I can flash the .zip files that before I was flashing with the recovery with this application?
Yeah, if those files are kernels. This tool has been tested with Apache14's 1.2 and 1.5 GHz OC/UV kernels.
jkoljo said:
Yeah, if those files are kernels. This tool has been tested with Apache14's 1.2 and 1.5 GHz OC/UV kernels.
Click to expand...
Click to collapse
Wow it's amazing guy!!! i have tried now, with, before my htc desire hd was going in eternal bootloop with origianl rom and 1,2 kernel now it's ok really tank you!!!
No problem, glad it helped!
Hi,
support for german users here > www.handy-faq.de
with friendly greet
starbase64
Noob question but how can you revert back to original kernal?
Not tried this yet But this is What I been waiting for. How long does the process take?
Thanks
Sent from my Desire HD using XDA App
Used this tool to flash the Buzz 1.51GHz Kernel. First off, congrats on such an easy to use tool for noobs like me. It's really simple and straightforward. However, I now have a problem with my wifi not working (just shows 'error' in wifi settings). I'm guessing this is because the module didn't apply properly? I've tried it a couple of times now with the same result...although I fully accept it could be stupidity on my part.
Further info:
I have root (permenant, via visionary+) and S-off (Eng HBoot installed) but not installed clockwork recovery yet.
I start the app, set my DHD to 'charge only', tick 'I understand the risks' and click next.
Browse to the file I downloaded for the Kernel (this one) and click 'next'.
click 'go to fastboot' (phone reboots in fastboot mode) click 'Flash' and something about 'writing zimage' flashes past. Click Next. (phone reboots)
When phone reboots I enter my PIN, unlock the phone and select 'charge only' for the USB connection (this isn't mentioned, but I figure it needs to be connected like this for the adb stuff to work) and press 'apply modules'. Something on my phone requests superuser access (not sure if this is just co-incidence or something the app is doing) so I allow it. Loads of messages flash past on my desktop (I assume this is applying the modules) and the app says 'modules pushed and applied'.
My wifi status shows 'error' so I try a reboot. Still shows error.
Any ideas?
Deicist said:
Used this tool to flash the Buzz 1.51GHz Kernel. First off, congrats on such an easy to use tool for noobs like me. It's really simple and straightforward. However, I now have a problem with my wifi not working (just shows 'error' in wifi settings). I'm guessing this is because the module didn't apply properly? I've tried it a couple of times now with the same result...although I fully accept it could be stupidity on my part.
Further info:
I have root (permenant, via visionary+) and S-off (Eng HBoot installed) but not installed clockwork recovery yet.
I start the app, set my DHD to 'charge only', tick 'I understand the risks' and click next.
Browse to the file I downloaded for the Kernel (this one) and click 'next'.
click 'go to fastboot' (phone reboots in fastboot mode) click 'Flash' and something about 'writing zimage' flashes past. Click Next. (phone reboots)
When phone reboots I enter my PIN, unlock the phone and select 'charge only' for the USB connection (this isn't mentioned, but I figure it needs to be connected like this for the adb stuff to work) and press 'apply modules'. Something on my phone requests superuser access (not sure if this is just co-incidence or something the app is doing) so I allow it. Loads of messages flash past on my desktop (I assume this is applying the modules) and the app says 'modules pushed and applied'.
My wifi status shows 'error' so I try a reboot. Still shows error.
Any ideas?
Click to expand...
Click to collapse
Same issue here, does not push the wifi module
Strange, it does push it for me. I'll investigate. It may have something to do with root rights, does bcm4329.ko appear to your sdcard?
Nope, doesn't appear in sdcard.
For further info I tried it with 0.3 as well, same result.
Also, none of the modules get pushed, it's not just the wifi one.
My app removes the files from sdcard afterwards, so they might not be there anymore when you check it. I have now uploaded a new version with completely new SuperUser access code, also a lot of the code has been optimized.
This version works for me 100%, I just flashed from Apache14's kernel to kamma's kernel and back, wifi worked every time.
Also keep in mind that you should wait for the Android system to fully boot up before trying to push and apply the modules. So wait for "Usb debugging connected" and "Charge only"
Please give feedback!
jkoljo said:
My app removes the files from sdcard afterwards, so they might not be there anymore when you check it. I have now uploaded a new version with completely new SuperUser access code, also a lot of the code has been optimized.
This version works for me 100%, I just flashed from Apache14's kernel to kamma's kernel and back, wifi worked every time.
Also keep in mind that you should wait for the Android system to fully boot up before trying to push and apply the modules. So wait for "Usb debugging connected" and "Charge only"
Please give feedback!
Click to expand...
Click to collapse
Nope, will not push wifi module, all phone settings are as per instructions
Which rom are you on? Do you have HTC Sync 3.0 on your computer?
Try pushing modules manually as per Apache14's thread first post, if it works then the problem is propably in my tool, if it does not work, the problems is at your end.
Have a US Cellular HTC Desire CDMA.
Android 2.2
HBoot - 1.06.0000
Radio - 2.15.00.11.16
Unrevoked method of Rooting fails.
Other thoughts?
Unfortunately, I do not have an answer. I am having the same issue. If I find anything I will pass it on.
Okay I've got temporary root at least. An app called visionary, not available on the market so google that to find a download, it is a one click solution. Temp Root option works but Permanent Root does not. It takes longer to boot and has to run every time you turn your phone on. Kinda a pain but its steps in the right direction.
So as I was searching the Cyanogen forums I got a suggestion. It ended up working great for me. I ran Z4root. I ran the app selected the permanent option and let it run for about 2 min. It will just stay "rooting". I shut the phone off and restarted it. Once the phone was loaded I ran SuperUser and it ran fine. I ran AdFree, Quickboot, and Titanium backup. the only issue is with Titanium back up and it only restored some apps before closing. Not a big deal because I only wanted a few. I think it would work if I backed up on 2.2 rather than bringing 2.1 saved app with data and try to restore on 2.2. All credit goes to dontbrickit on cyanogen forums. I used the quickboot and rebooted the phone and I still had root, so it does not seem to be temporary.
I tried z4root with no results. It says rooting, goes through the whole process then reboots. No root after. Temp root feature doesn't function either. Are you running the newly released uscell rom?
HBOOT 1.06 fail
Although I have never posted I have followed the works and efforts of the very skilled developers and pro-active user for some time now and I would like to say my hats off to you all, this is by far one of the most productive and progressive communities have seen yet, I digress. I’m having an issue with hboot 1.06 also, I was running CM6 (very happy with it I might add) but when uscc came with the OEM 2.2 I rolled back to 2.1 so that I could go forward with the provider update. This process went fine, I cleared tcash and sys cash wiped and installed OEM. Turns out uscc OEM sucks bad. I only did it for htc sense and it s NOT WORHT IT. HTC sense is cool but not worth the internal memory loss I have taken. CM6 had me at over 275mb free on fresh install, OEM 145ish….FAIL. not to mention its laggy as hell on the surface. So want to go to CM7 the issue is when did the OEM it broke my hboot, when go to recovery it takes me to some blue text I can choose but its update.zip CC, reboot and factory reset. I have used clockwork 15 ways, tried 3 htc syncs that all connect but the same thing happens,,,, when any of these apps get to the hboot it does the same thing BLUE TEXT, I have tried to port old backups as well and nothing can get past this broken hboot 1.06. any suggestions?
have a thread for this going here
rhoover said:
have a thread for this going here
Click to expand...
Click to collapse
.......had
This is how I rooted mine
Guide to rooting Branded 2.2 Froyo Desire with 1.06 HBoot
My Software Information
Android Version - 2.2
Baseband Version - 2.15.00.11.16
Kernal Version - 2.6.32.21-g7a207a4 | [email protected] #1
Build Number - 2.11.573.5 CL325935 release-keys
Software Number - 2.11.573.5
Browser Version - Webkit 3.1
PRI Version - 1.70_027
PRL Version – 15106
My HBoot Information
Bravoc DVT2 SHIP S-OFF
HBOOT-1.06.0000
Microp-051e
Touch Panel-Synt0101
Radio-2.15.00.11.16
Dec 22 2010, 16:16:39
Info - I have a US Cellular Branded CDMA Desire. I have owned it for 3 months. Came with 2.1 Eclair, I was unhappy waiting for 2.2 so I rooted and flashed a couple different roms. I ended up with a Custom Froyo w/ Sense and a few Gingerbread features. I found out about update release for US Cellular so before updating I reset factory settings restoring phone to stock Eclair. Took phone to store, they upgraded to Froyo I played for a few days until I wanted to reroot my phone. Unsuccessful on at least 5 different tries with both Windows/Linux and many different options of unrevoked and settings. Found out that 1.06 HBoot was unsupported by unrevoked. So I studied what other people posted about their attempts and ideas. Found one person claiming to have rooted theirs. Unfortunately he did not give many details in his post about the exact process. Here are the steps I took to successfully root my phone.
Backup any data, media, programs you wish to your SD card.
Transfer your backup from your SD card to your PC.
Go to Settings>SD & Phone Storage
Click “Unmount SD Card”
Click “Format SD Card”
This will clear anything you may have saved to it, which might interfere with rooting/flashing
Once Formatting is complete
Click “Mount SD Card”
Now it is time to reset phone to stock 2.2
Go to Settings>SD & Phone Storage (You should already be there, unless you went back/home)
Click “Factory Data Reset”
Click “Reset Phone” in next menu
Phone should reset and reboot bringing you into a tutorial (US Cellular, unsure on other carriers)
Skip through all prompts
DO NOT edit/change/add anything
You should now be at the Home Screen
Go to Settings>Applications>Development - Enable (Green Check) “USB debugging”
Go to Settings>Applications - Enable (Green Check) “Unknown Sources”
Go to Settings>Connect to PC>Default Connection Type – Select (Green Circle) “Charge Only”
Go to Settings>Connect to PC – Disable (NO Green Check) “Ask Me”
Press Home Button
Put Phone Down
Leave Phone On (Do not power down) & Do Not Touch Phone until Told To
Your phone is ready to begin rooting.
You can attempt to use Windows if you really wish, but I find Linux to be a no-hassle idiot proof OS. Many people run across issues with either drivers, or sync, or possibly other factors.
Linux solves this issue by having an all-in-one OS. It already contains the drivers needed, and does not require installing or uninstalling of anything.
Evidently there’s a **** ton of options when it comes to Linux.
I used Ubuntu Desktop Edition 32-bit
I recommend using the same because my steps follow that.
Go to Ubuntu Dot Com *I can't post links yet"
Ensure Latest Version (10.10 when guide was made)
Ensure correct bit (32 or 64)
Click “Start Download”
If 10.10 32bit (693 MB)
If 10.10 64bit (695 MB)
Once download complete you will need to Burn the ISO as an “image” to a CD.
If unsure how to do this seek help elsewhere (it’s very simple)
You should now have a bootable trial Ubuntu CD
If your Internet is Wired you are set to continue if Internet is Wireless Router I recommend obtaining unrevoked because restart.
If Wireless
Go to Unrevoked Dot Com *I can't post links yet" and click “Download for Linux”
Save to Desktop
Once complete transfer “reflash.tar.gz” to USB Stick Drive
Remove Stick Drive
Insert Ubuntu into CD drive and close drive
Take steps needed to ensure Boot CD is activated upon restart
Once ready restart PC
CD should boot and “Welcome” screen displayed
Select “English”
Click “Try Ubuntu”
You should be brought to a “Desktop” containing two icons “Examples & Install Ubuntu 10.10”
If Wired
Click “Mozilla Icon” on the taskbar on the top of screen
Go to Unrevoked Dot Com and click “Download for Linux”
Open “Reflash.tar.gz” and Extract to Desktop
Close ALL open windows
Go to Applications>Accessories – Click “Terminal”
In the “Command Prompt Looking” Window type the following lines each follow by “Enter”
cd Desktop
chmod +x reflash
sudo ./reflash
Please Leave Terminal open
Unrevoked 3 should now be open
Connect USB Cable to Computer
With USB Cable connected
Connect Phone to USB (Yes you can now touch your Phone)
Unrevoked should recognize Phone and a “Prompt” should be displayed
Click “Ok/Yes” whatever it says I forgot I was so excited to not see another FAIL MSG
Sit Still DO NOT touch ANYTHING
Be patient phone will reboot multiple times
Should eventually see Phone Boot into the HBoot Menu
It will install clockworkmod
Phone will enter recovery menu
Unrevoked Window will hopefully eventually say something like
“Complete Safe to Disconnect and Reboot”
NOTE – Both my Terminal on Ubuntu & Recovery displayed multiple “Installation Aborted”, “Update Failed”, “ERROR”, and “Unsupported” lines in the log.
At this point you should be Successfully Rooted, and safe to reboot.
Superuser should be displayed in the app list
I’m not sure in what order I did what but I installed “Titanium Backup Free Edition” “Busy Box” and “Root Check” and played with each until Root Check displayed that I had both “Root Access and Busy Box Installed”
I do hope this works for you as it did for me. I refused to stay “unsupported by unrevoked” until a fix was available. I will try to help anyone with clarification in steps, or any questions/problems. I did find out that a version of Linux called “Slax” is available that has “root permissions” contained already. Which eliminates the entire “Terminal” step making it unneeded?
ethahes said:
Guide to rooting Branded 2.2 Froyo Desire with 1.06 HBoot
My Software Information
Android Version - 2.2
Baseband Version - 2.15.00.11.16
Kernal Version - 2.6.32.21-g7a207a4 | [email protected] #1
Build Number - 2.11.573.5 CL325935 release-keys
Software Number - 2.11.573.5
Browser Version - Webkit 3.1
PRI Version - 1.70_027
PRL Version – 15106
My HBoot Information
Bravoc DVT2 SHIP S-OFF
HBOOT-1.06.0000
Microp-051e
Touch Panel-Synt0101
Radio-2.15.00.11.16
Dec 22 2010, 16:16:39
Info - I have a US Cellular Branded CDMA Desire. I have owned it for 3 months. Came with 2.1 Eclair, I was unhappy waiting for 2.2 so I rooted and flashed a couple different roms. I ended up with a Custom Froyo w/ Sense and a few Gingerbread features. I found out about update release for US Cellular so before updating I reset factory settings restoring phone to stock Eclair. Took phone to store, they upgraded to Froyo I played for a few days until I wanted to reroot my phone. Unsuccessful on at least 5 different tries with both Windows/Linux and many different options of unrevoked and settings. Found out that 1.06 HBoot was unsupported by unrevoked. So I studied what other people posted about their attempts and ideas. Found one person claiming to have rooted theirs. Unfortunately he did not give many details in his post about the exact process. Here are the steps I took to successfully root my phone.
Backup any data, media, programs you wish to your SD card.
Transfer your backup from your SD card to your PC.
Go to Settings>SD & Phone Storage
Click “Unmount SD Card”
Click “Format SD Card”
This will clear anything you may have saved to it, which might interfere with rooting/flashing
Once Formatting is complete
Click “Mount SD Card”
Now it is time to reset phone to stock 2.2
Go to Settings>SD & Phone Storage (You should already be there, unless you went back/home)
Click “Factory Data Reset”
Click “Reset Phone” in next menu
Phone should reset and reboot bringing you into a tutorial (US Cellular, unsure on other carriers)
Skip through all prompts
DO NOT edit/change/add anything
You should now be at the Home Screen
Go to Settings>Applications>Development - Enable (Green Check) “USB debugging”
Go to Settings>Applications - Enable (Green Check) “Unknown Sources”
Go to Settings>Connect to PC>Default Connection Type – Select (Green Circle) “Charge Only”
Go to Settings>Connect to PC – Disable (NO Green Check) “Ask Me”
Press Home Button
Put Phone Down
Leave Phone On (Do not power down) & Do Not Touch Phone until Told To
Your phone is ready to begin rooting.
You can attempt to use Windows if you really wish, but I find Linux to be a no-hassle idiot proof OS. Many people run across issues with either drivers, or sync, or possibly other factors.
Linux solves this issue by having an all-in-one OS. It already contains the drivers needed, and does not require installing or uninstalling of anything.
Evidently there’s a **** ton of options when it comes to Linux.
I used Ubuntu Desktop Edition 32-bit
I recommend using the same because my steps follow that.
Go to Ubuntu Dot Com *I can't post links yet"
Ensure Latest Version (10.10 when guide was made)
Ensure correct bit (32 or 64)
Click “Start Download”
If 10.10 32bit (693 MB)
If 10.10 64bit (695 MB)
Once download complete you will need to Burn the ISO as an “image” to a CD.
If unsure how to do this seek help elsewhere (it’s very simple)
You should now have a bootable trial Ubuntu CD
If your Internet is Wired you are set to continue if Internet is Wireless Router I recommend obtaining unrevoked because restart.
If Wireless
Go to Unrevoked Dot Com *I can't post links yet" and click “Download for Linux”
Save to Desktop
Once complete transfer “reflash.tar.gz” to USB Stick Drive
Remove Stick Drive
Insert Ubuntu into CD drive and close drive
Take steps needed to ensure Boot CD is activated upon restart
Once ready restart PC
CD should boot and “Welcome” screen displayed
Select “English”
Click “Try Ubuntu”
You should be brought to a “Desktop” containing two icons “Examples & Install Ubuntu 10.10”
If Wired
Click “Mozilla Icon” on the taskbar on the top of screen
Go to Unrevoked Dot Com and click “Download for Linux”
Open “Reflash.tar.gz” and Extract to Desktop
Close ALL open windows
Go to Applications>Accessories – Click “Terminal”
In the “Command Prompt Looking” Window type the following lines each follow by “Enter”
cd Desktop
chmod +x reflash
sudo ./reflash
Please Leave Terminal open
Unrevoked 3 should now be open
Connect USB Cable to Computer
With USB Cable connected
Connect Phone to USB (Yes you can now touch your Phone)
Unrevoked should recognize Phone and a “Prompt” should be displayed
Click “Ok/Yes” whatever it says I forgot I was so excited to not see another FAIL MSG
Sit Still DO NOT touch ANYTHING
Be patient phone will reboot multiple times
Should eventually see Phone Boot into the HBoot Menu
It will install clockworkmod
Phone will enter recovery menu
Unrevoked Window will hopefully eventually say something like
“Complete Safe to Disconnect and Reboot”
NOTE – Both my Terminal on Ubuntu & Recovery displayed multiple “Installation Aborted”, “Update Failed”, “ERROR”, and “Unsupported” lines in the log.
At this point you should be Successfully Rooted, and safe to reboot.
Superuser should be displayed in the app list
I’m not sure in what order I did what but I installed “Titanium Backup Free Edition” “Busy Box” and “Root Check” and played with each until Root Check displayed that I had both “Root Access and Busy Box Installed”
I do hope this works for you as it did for me. I refused to stay “unsupported by unrevoked” until a fix was available. I will try to help anyone with clarification in steps, or any questions/problems. I did find out that a version of Linux called “Slax” is available that has “root permissions” contained already. Which eliminates the entire “Terminal” step making it unneeded?
Click to expand...
Click to collapse
The reason that this worked for you was because you have previous used revoked and are now s-off. With s-off, you can reflash recovery and superuser without unrevoked being supported. Others will probably still have an issue.
ethahes said:
Guide to rooting Branded 2.2 Froyo Desire with 1.06 HBoot
My Software Information
Android Version - 2.2
Baseband Version - 2.15.00.11.16
Kernal Version - 2.6.32.21-g7a207a4 | [email protected] #1
Build Number - 2.11.573.5 CL325935 release-keys
Software Number - 2.11.573.5
Browser Version - Webkit 3.1
PRI Version - 1.70_027
PRL Version – 15106
My HBoot Information
Bravoc DVT2 SHIP S-OFF
HBOOT-1.06.0000
Microp-051e
Touch Panel-Synt0101
Radio-2.15.00.11.16
Dec 22 2010, 16:16:39
Info - I have a US Cellular Branded CDMA Desire. I have owned it for 3 months. Came with 2.1 Eclair, I was unhappy waiting for 2.2 so I rooted and flashed a couple different roms. I ended up with a Custom Froyo w/ Sense and a few Gingerbread features. I found out about update release for US Cellular so before updating I reset factory settings restoring phone to stock Eclair. Took phone to store, they upgraded to Froyo I played for a few days until I wanted to reroot my phone. Unsuccessful on at least 5 different tries with both Windows/Linux and many different options of unrevoked and settings. Found out that 1.06 HBoot was unsupported by unrevoked. So I studied what other people posted about their attempts and ideas. Found one person claiming to have rooted theirs. Unfortunately he did not give many details in his post about the exact process. Here are the steps I took to successfully root my phone.
Backup any data, media, programs you wish to your SD card.
Transfer your backup from your SD card to your PC.
Go to Settings>SD & Phone Storage
Click “Unmount SD Card”
Click “Format SD Card”
This will clear anything you may have saved to it, which might interfere with rooting/flashing
Once Formatting is complete
Click “Mount SD Card”
Now it is time to reset phone to stock 2.2
Go to Settings>SD & Phone Storage (You should already be there, unless you went back/home)
Click “Factory Data Reset”
Click “Reset Phone” in next menu
Phone should reset and reboot bringing you into a tutorial (US Cellular, unsure on other carriers)
Skip through all prompts
DO NOT edit/change/add anything
You should now be at the Home Screen
Go to Settings>Applications>Development - Enable (Green Check) “USB debugging”
Go to Settings>Applications - Enable (Green Check) “Unknown Sources”
Go to Settings>Connect to PC>Default Connection Type – Select (Green Circle) “Charge Only”
Go to Settings>Connect to PC – Disable (NO Green Check) “Ask Me”
Press Home Button
Put Phone Down
Leave Phone On (Do not power down) & Do Not Touch Phone until Told To
Your phone is ready to begin rooting.
You can attempt to use Windows if you really wish, but I find Linux to be a no-hassle idiot proof OS. Many people run across issues with either drivers, or sync, or possibly other factors.
Linux solves this issue by having an all-in-one OS. It already contains the drivers needed, and does not require installing or uninstalling of anything.
Evidently there’s a **** ton of options when it comes to Linux.
I used Ubuntu Desktop Edition 32-bit
I recommend using the same because my steps follow that.
Go to Ubuntu Dot Com *I can't post links yet"
Ensure Latest Version (10.10 when guide was made)
Ensure correct bit (32 or 64)
Click “Start Download”
If 10.10 32bit (693 MB)
If 10.10 64bit (695 MB)
Once download complete you will need to Burn the ISO as an “image” to a CD.
If unsure how to do this seek help elsewhere (it’s very simple)
You should now have a bootable trial Ubuntu CD
If your Internet is Wired you are set to continue if Internet is Wireless Router I recommend obtaining unrevoked because restart.
If Wireless
Go to Unrevoked Dot Com *I can't post links yet" and click “Download for Linux”
Save to Desktop
Once complete transfer “reflash.tar.gz” to USB Stick Drive
Remove Stick Drive
Insert Ubuntu into CD drive and close drive
Take steps needed to ensure Boot CD is activated upon restart
Once ready restart PC
CD should boot and “Welcome” screen displayed
Select “English”
Click “Try Ubuntu”
You should be brought to a “Desktop” containing two icons “Examples & Install Ubuntu 10.10”
If Wired
Click “Mozilla Icon” on the taskbar on the top of screen
Go to Unrevoked Dot Com and click “Download for Linux”
Open “Reflash.tar.gz” and Extract to Desktop
Close ALL open windows
Go to Applications>Accessories – Click “Terminal”
In the “Command Prompt Looking” Window type the following lines each follow by “Enter”
cd Desktop
chmod +x reflash
sudo ./reflash
Please Leave Terminal open
Unrevoked 3 should now be open
Connect USB Cable to Computer
With USB Cable connected
Connect Phone to USB (Yes you can now touch your Phone)
Unrevoked should recognize Phone and a “Prompt” should be displayed
Click “Ok/Yes” whatever it says I forgot I was so excited to not see another FAIL MSG
Sit Still DO NOT touch ANYTHING
Be patient phone will reboot multiple times
Should eventually see Phone Boot into the HBoot Menu
It will install clockworkmod
Phone will enter recovery menu
Unrevoked Window will hopefully eventually say something like
“Complete Safe to Disconnect and Reboot”
NOTE – Both my Terminal on Ubuntu & Recovery displayed multiple “Installation Aborted”, “Update Failed”, “ERROR”, and “Unsupported” lines in the log.
At this point you should be Successfully Rooted, and safe to reboot.
Superuser should be displayed in the app list
I’m not sure in what order I did what but I installed “Titanium Backup Free Edition” “Busy Box” and “Root Check” and played with each until Root Check displayed that I had both “Root Access and Busy Box Installed”
I do hope this works for you as it did for me. I refused to stay “unsupported by unrevoked” until a fix was available. I will try to help anyone with clarification in steps, or any questions/problems. I did find out that a version of Linux called “Slax” is available that has “root permissions” contained already. Which eliminates the entire “Terminal” step making it unneeded?
Click to expand...
Click to collapse
Does not work on USCC HTC Desire CDMA with HBOOT 1.06 that are S-ON.
We need a way for those of us USCC HTC Desire users who have Froyo as a stock ROM with HBOOT 1.06 S-ON to get that set to S-OFF. Currently no product to do so exists and while I was pointed to the #bravoc IRC channel by the users at #unrevokedtest, there wasn't anyone home. Though I have been reading at AndroidForums that someone named Matt is currently working on one. I'm not going to hold my breath at this point...
I think unrevoked is working on it. However, it could be awhile till a new exploit is found.
Sent from my HTC Desire CDMA using XDA Premium App
I was able to gain temporary root with z4root.1.3.0.apk
BravoC DVT2 S-ON
HBOOT-1.06.0000
RADIO-2.15.00.11.16
permanent root didn't work out with this app.
Glad I found this thread. Add me to the list. Ran UnrEVOked and no go. I get a "Failed to Unlock NAND" message. Hope the UnrEVOked guys come up with something.
BRAVOC DVT2 SHIP S-ON
HBOOT-1.06.0000
MICROP-051e
TOUCH PANEL-SYNT0101
RADIO-2.15.00.11.16
Stuck with STOCK Froyo 2.2 and HBOOT 1.06 + S-ON
Aaargh!!! This is so aggravating! I'm in the exact same position, guys. Need some help... Anybody...
I am as well, I use an EVO, but a lot of my friends are picking up Desires cause of a ZERO cost promo.
All ship 1.06
all have S-ON
Anyone with the 1.06 HBOOT should try out this exploit: http://forum.xda-developers.com/showthread.php?t=1044765
It says it may work on some Froyo builds and it is the first new exploit I've seen in awhile. I say give it a shot.
WARNING: CAN CAUSE SDCARD TO BE FORMATTED SO BACK UP FIRST AND READ ALL INSTRUCTIONS!
Post your results if you have any luck!
wont fix the s-on problem according to the first post, so even if you get root access it'll be removed once you reboot :/
grafton1046 said:
wont fix the s-on problem according to the first post, so even if you get root access it'll be removed once you reboot :/
Click to expand...
Click to collapse
It is possible to have permanent root access without s-off. The goal of getting root is so a custom recovery can be installed.
ah, so what can be done with root access when you can't access the system folder to make changes? Or am I missing something about the whole process...
Sent from my HTC Desire using XDA App
Hi XDA,
so basically i bought a Velocity Cruz T301 recently and followed the known procedures for rooting, flashing ClockworkMod Recovery and custom rom (SJHill Rom v0.3).
before the full brick my device was at ClockworkMod 5 and rooted with SJHill Rom v0.3.
i installed CWM by flashing the zip in stock recovery, then succesfully rooted the device, finally wiped and flashed my custom rom
after major dissapointment in this tablets performance i decided i wanted to get rid of it.
So i downloaded the stock rom, wipe and flashed it onto the tablet...
the tablet turned off when it was finished (i think it was attempting to reboot) and never turned back on again...EVER! :good:
i cant even get to recovery
i tried flashing with adb and fastboot but the device is never even presents itselft to the computer.
i found out that you can boot the device into USB boot mode where you hold the "VOL -" (Volume Down) button and press the reset button and while connected to the computer (windows only) a "JZ4760 USB Boot Device" appears.
i did some googling and also found out that the T301 is based on similar tech to a bunch of tablets and they can all be modified by some software released by Ingenic called USBBootTool.exe
the tool is written in chinese and i cant decypher it all, though i found out how to use it based on its usage for other Ingenic based tablets
1.) you will need to disable driver signature verification (press F8 on boot of windows and toggle the setting, i hate rebooting too but it has to be done)
2.) boot your tablet into USB Boot Mode (hold down Vol - and press Reset button)
3.) install the driver for your device (included in the files below)
4.) with the tablet disconnected you would open the USBBootTool.exe
5.) select your tablet in the options and fill each box with the files needed to flash (files included below)
6.) reconnect the tablet while still in USB Boot Mode and the software will flash your device on detection
everything goes fine for me except when i get to the flashing part in the end.
when USBBootTool detects my tablet, it attempts to flash and gives me a stream of errors and never flashes my device.
i dont know what to do at this point. i have provided direct links to all the software im using and also links to where i got them.
any help would be appreciated, thank you to the XDA community in advance
>------------------- DOWNLOADS ------------------------<
USBBootTool.exe / Tablet Drivers (4725 / 4725B / 4740 / 4750 / 4755 / 4760 / 4770)
http://dl.dropbox.com/u/79196608/burn_tools_3.0.16.rar
obtained from - http://forum.xda-developers.com/showthread.php?t=1720621
Velocity Cruz T301 Update.zip (contains the system.img / data.img / mbr-xboot.bin files)
http://www.cruztablet.com/T301update.zip
obtained from - http://www.cruztablet.com/Article_861.php
SJHill Rom v0.3
http://www.androidfilehost.com/?fid=9390362690511176486
obtained from - http://www.slatedroid.com/topic/27583-rom-t301-sjhill-rom-17-feb-2012-download-link-updated/
ClockworkMod 5
http://files.androtab.info/ingenic/cwm/20120514/T301-recovery-signed.zip
obtained from - http://androtab.info/mips/ingenic/clockworkmod/
I have the same situation. I have gone through every menu in the USB Boot tool and to no avail am I able to recover my T100.
gmick is redoing the software because the coding is set up wrong. Once he gets that figured out there should be a fool proof unbricking method that we can follow. He is posting information over on Slate Droid if you want to take a look.
feyerbrand said:
gmick is redoing the software because the coding is set up wrong. Once he gets that figured out there should be a fool proof unbricking method that we can follow. He is posting information over on Slate Droid if you want to take a look.
Click to expand...
Click to collapse
ok post the link to the thread, and ill add it to the first post as a solution if its found to be a working one
JustSayTech said:
ok post the link to the thread, and ill add it to the first post as a solution if its found to be a working one
Click to expand...
Click to collapse
*Cross Post from SlateDroid* (but I can't post the link because XDA won't allow it)
I found out why the USB boot isn't working. Well, more appropriately I know where it fails but not exactly "why".
The USB Boot tool works like this:
1) Send x00 command (Get CPU Info)
2) Device responds with "JZ4760V1"
3) Host sends two binaries, stage1 and stage2. Stage 1 sets up memory stuff, and Stage 2 sets up USB flashing functions.
4) Host checks that the binaries executed by issuing another x00 command (Which serves as an "Are you still there?" function)
5) If the response is good, the host will flash the images, if the response is bad, it will abort.
Our devices are failing at step 4. The linux usb boot tools (xburst-tools) fail in an identical fashion.
I know that the first stage binary transfers and executes fine because if it didn't the device would be limited to 16k. The second stage is 120K and is transferred successfully. Once the second stage "execute" command is sent, the device crashes.
The second stage is also unique to the CPU type. I've used all of the binaries for JZ4760 I could find on the net and when that failed I cross compiled my own binary from source and it still crashed.
At this point I highly doubt I'll ever be able to fix it, and this completely explains why no one could get any usb recovery tool to work while others using similar devices could. I guess our board is modified just enough for ingenic's stock binaries to fail. Without knowing what's changed (getting Velocity Micro's source) we're SOL.
I can open it up again and solder on the serial header but I'm betting it's going to give me some generic "couldn't execute" message that isn't going to help me. I'll probably do this anyway though because I've come this far so what's the loss.
wow, i learned alot from that post, seems like writing a usbboottool-like application that can send the commands but also log and possibly bypass security checks etc but that def would take sometime. thank you for your insight, seems youve come the closest to cracking the case, actually you found the fault, hopefully your methods can eventually bring about a fix
JZ 4770
gmick said:
*Cross Post from SlateDroid* (but I can't post the link because XDA won't allow it)
I found out why the USB boot isn't working. Well, more appropriately I know where it fails but not exactly "why".
The USB Boot tool works like this:
1) Send x00 command (Get CPU Info)
2) Device responds with "JZ4760V1"
3) Host sends two binaries, stage1 and stage2. Stage 1 sets up memory stuff, and Stage 2 sets up USB flashing functions.
4) Host checks that the binaries executed by issuing another x00 command (Which serves as an "Are you still there?" function)
5) If the response is good, the host will flash the images, if the response is bad, it will abort.
Our devices are failing at step 4. The linux usb boot tools (xburst-tools) fail in an identical fashion.
I know that the first stage binary transfers and executes fine because if it didn't the device would be limited to 16k. The second stage is 120K and is transferred successfully. Once the second stage "execute" command is sent, the device crashes.
The second stage is also unique to the CPU type. I've used all of the binaries for JZ4760 I could find on the net and when that failed I cross compiled my own binary from source and it still crashed.
At this point I highly doubt I'll ever be able to fix it, and this completely explains why no one could get any usb recovery tool to work while others using similar devices could. I guess our board is modified just enough for ingenic's stock binaries to fail. Without knowing what's changed (getting Velocity Micro's source) we're SOL.
I can open it up again and solder on the serial header but I'm betting it's going to give me some generic "couldn't execute" message that isn't going to help me. I'll probably do this anyway though because I've come this far so what's the loss.
Click to expand...
Click to collapse
for my JZ4770 Earlier USB tool was flashing .img without any problem but for now it is saying "load cfg failed". "API downlaod failed' like dialogues and doesnt flash anything. Any idea? Thanks in advance!!
First restart your computer (actually restart it) then redownload the USB boot tool and save it in a completely new directory and use a different USB port
Sent from my Pokeball
Yes, I did
JustSayTech said:
First restart your computer (actually restart it) then redownload the USB boot tool and save it in a completely new directory and use a different USB port
Sent from my Pokeball
Click to expand...
Click to collapse
Yes, I tried with this suggestion. Rather I reinstalled xp and the tried again. But the dialogues are same. The history is like this. Was having ICS on JZ 4770. Formatted with usb tool and put JB updates. It was not sensing touch so reflashed another JB updates. Now the tab boots, it reaches to boot logo for around 12 seconds and restarts in stock recovery. While it is in booting stage it get detected by windows and adb also. In stock recovery mode it get detected by windows and in turn by adb also. If I tried to install updates through SD card it shows it had installed and reboots after completion. But again the same way it goes to boot logo and then back to stock JB recovery. It also boots in ingenic boot device mode and gets detected by USB burn tools. But when try to flash any of the ROM it gives the same dialogues "check cfg failed" "api download failed" "boot. fw failed" and cant flash anything.
Is there any tool which can be flashed or a script which can be used from SD card for completely formatting flash memory so that USB burn tool can flash required ROM?
can you flash the stock rom in recovery?
Managed using USB BOOT TOOL for ingenic JZ 4770 board in English
JustSayTech said:
can you flash the stock rom in recovery?
Click to expand...
Click to collapse
thanks man but I managed to boot the device. I used following USB BOOT TOOL for ingenic 4770 boards. The goodness with this tool, this is completely in English. You will know what you are doing. Even after opening the main window of the tool you can right click and then get another options(yes again in English). My problem with this device was bad blocks at 1024. In the options there is chance to force erase whole the nand partitions which I used and erased all the partitions thereby made all the partions available for flashing and readable by the tool. Then from File option selected stock rom files and flashed them. While flashing selected JZ4770 iNanad.ini file in manual configuration. This tool has really helped me to come out of the issue and will be useful for guys using JZ 4770 board.
http://www.4shared.com/rar/m1BUV5r2/USBBurnTool_20120401_for_relea.html
Got USBBootTool.exe kind of working.
1. Download the following file from Ingenic.
ftp * ingenic * cn/3sw/01linux/tmp/jz4770-20110610.rar
2. Download Applocale from Microsoft.
www * microsoft * com/en-us/download/details.aspx?id=13209
3. Extract the jz4770-20110610.rar and find the folder. (Using 7zip should keep the UTF encoding in Chinese)
20110610\04burn\20110524_4770_Programmer
4. Copy the folder 20110524_4770_Programmer to location you want to use it in.
5. Install Microsoft Applocale (Just in case, I don't think it is required)
Now Start Applocale and create a shortcut to USBbootTool.exe inside 20110524_4770_Programmer
中文(简体) is simplified Chinese option and should let you view the GUI correctly.
6. Now with the Applocale Shortcut created for USBbootTool.exe you can start the application with correct fonts.
Now this is where is breaks down.
TABLET-8 NAND FINAL BSP(S3 TEST) will allow you to read from it and write to it, but the CFG is off.
\tool_cfg\tablet-8-nand-final.ini is the configuration for it.
DO NOT CONNECT THE DEVICE WITH ANY OPTIONS CHECKED OR LOAD ANY FILES.
See Attached Images.
Next to the Read button is some Boot Option menu. I am not fulling aware of what this does.
What I need is a someone to help me fix/correct the ini/cfg files in
\20110524_4770_Programmer\tool_cfg\.ini
\20110524_4770_Programmer\4760\
to correctly match the files of the NAND.
Also if anyone has a copy (dd to img) or (cat to img) of the block devices.
That would help a ton.
# cat /proc/partitions
# cat /proc/mtd
I would also love another T10x Tablet for cheap.
I want to start building things like new bootloader, kernel, system image,
performance libraries to take full use of the Ingenic JZ4760 (www * ingenic * cn/product.aspx?CID=11)
I also bring Christmas gifts
2 APKS. You can place them in /system/app or /data/app.
Google Play will crash now and again, but it will load and work. (Vending.apk)
Secondly I bring the gift of performance increase, just by a slight bit.
edit the line of the heapsize in /system/build.prop dalvik.vm.heapsize=96m
Remember to make sure the permissions are set back to 666 or 644.
Original Vending.Apk before updates came from here: (Incase you are paranoid)
code * google * com/p/ics-nexus-s-4g/source/browse/trunk/system/app/Vending.apk?spec=svn20&r=18
ics-nexus-s-4g * googlecode * com/svn-history/r18/trunk/system/app/Vending.apk
To prevent spam on the XDA forums, ALL new users prevented from posting outside links in their messages. After approximately 10 posts, you will be able to post outside links. Thank you for
Click to expand...
Click to collapse
Stupid. how do you expect real people to help post Tech Docs? That is bad Moderating and Administrating.
Make sure to replace the Asterisk's with spaces to normal dots.
Requesting Block Images.
Does anyone have a copy of it they can send me for a T10x?
block images......
IceGryphon said:
Does anyone have a copy of it they can send me for a T10x?
Click to expand...
Click to collapse
Which block images do you want?
...also is there a way to rip the stock images off the jz4760 in the t301.
Such as:
Can i usethe ingenic uboot tool?
Anybody find the jtag pins?
Is the 4 pin conn next 2 the batt for serial?
.......i guess ill try to take a look this weekend
Ics would be really nice, but probably slower than stock..... especially with the limited ram
I unpacked the stock rom. I also unpacked an ics rom for a jz4770, and repo sync'd the aosp and mips 3.0.8 android kernel.
I'm still trying to figure out specs for the processor though. I know that its mips32 - el- fp- r1, but i cannot figur out the dsp version ... if it has one?
Error in erasing nand
nanachitang420 said:
thanks man but I managed to boot the device. I used following USB BOOT TOOL for ingenic 4770 boards. The goodness with this tool, this is completely in English. You will know what you are doing. Even after opening the main window of the tool you can right click and then get another options(yes again in English). My problem with this device was bad blocks at 1024. In the options there is chance to force erase whole the nand partitions which I used and erased all the partitions thereby made all the partions available for flashing and readable by the tool. Then from File option selected stock rom files and flashed them. While flashing selected JZ4770 iNanad.ini file in manual configuration. This tool has really helped me to come out of the issue and will be useful for guys using JZ 4770 board.
http://www.4shared.com/rar/m1BUV5r2/USBBurnTool_20120401_for_relea.html
Click to expand...
Click to collapse
I used english ingenic tool to erase bad blocks but m nt able erase bad blocks live suit is giving eror id=0x4848
The intention behind this thread is to share some experience of a little project where I try to migrate the Sony Xperia Shinano devices (based on Qualcomm MSM8974 chipset with a Broadcom BCM4339 wifi/bluetooth chip) from the old bcmdhd wifi driver to a close-to-mainline brcmfmac driver. I want to share the progress and status here, and maybe get some hints. It is work in progress, and for sure it still contains some mistakes - I haven't done something like this before and am still learning.
Why?
The Shinano devices are still maintained by the LineageOS, and some devices are currently on the official LineageOS 17.1 stream.
The kernel however is terribly outdated, based on msm-3.4
There are some wifi issues with all LineageOS-based ROMs since years, like weak 5GHz connections and non-working wifi in some countries. There are some hacks around that, but they work (afaik) by practically disabling the kernel-level regulatory system by e.g. setting a static country code like "DE".
I am curious if we can improve that by updating the kernel drivers and network/wifi components, and maybe also the firmware (to the latest release available from Broadcom, 6.37.34.43 ?) . I got the ideas from Sonyxperiadev/Loire (+ related platform config), the Linux Backport Project and other MSM8974 based devices.
Working so far:
Did a few tests only so far, STA with WPA2 and p2p (hotspot) seem to work
Wifi connection is stable on 2,4GHz on 00 world regulatory domain (tested on a Z3 and a Z3c)
5GHz manually setting a country code (could only test DE)
Switching countries / setting new regulatory domains is now working, too
Download speed looks OK to me, in my case at least better than before Download >60MBit, Upload >30 Mbit on some initial tests.
Not working yet:
WifiHAL (qcom-caf) does not work correctly. This may create multiple issues, tbd.
Connection bandwidth seems to be not reported correctly
I don't know if wowlan works (interrupts working?)
Stability: After 1-2 days without reboot wifi sometimes crashes but immediately reconnects. Reason not yet understood.
Patches & Picks
Kernel:
backported and configured brcmfmac, cfg800211 wireless configuration API and wireless network stack from linux-stable v5.8 by adopting the compatibility patches from the linux backporting project.
updated Shinano device tree, updated Z3, Z3c and Z2 (Z2 test needed!) defconfigs (unset bcmdhd and enabled brcmfmac) and removed board-sony_shinano-wifi.o in the arch-msm makefile
Note: the backported drivers and compatibility-patches are located in a separate backports/ subdirectory
Sorry, this is work in progress and contains some hacks, to be cleaned up later
--> https://github.com/LineageOS/androi...1...Tom1000:lineage-17.1-driver-backport-v5.8
Vendor blobs / device z3(c): removed proprietary firmware and replaced that by publicly available firmware for bcm4339 on linux-firmware.git
z3c --> https://github.com/LineageOS/androi.../lineage-17.1...Tom1000:lineage-17.1-brcmfmac
z3 --> https://github.com/LineageOS/androi.../lineage-17.1...Tom1000:lineage-17.1-brcmfmac
Shinano-common: Use qcwcn instead of bcmdhd WLAN device, serve wpa_supplicant_overlay.conf
--> https://github.com/LineageOS/androi.../lineage-17.1...Tom1000:lineage-17.1-brcmfmac
msm8974-common: raise wpa_supplicant version (unknown if we need that) and update sysfs node for MAC address
--> https://github.com/LineageOS/androi.../lineage-17.1...Tom1000:lineage-17.1-brcmfmac
As a follow up, the driver seems to work quite stable already. I still have issues with nl80211 private commands, as a mainline brcmfmac does not seem to accept command strings passed via a libnl control socket like this:
qcwcn/wpa_supplicant_8_lib/driver_cmd_nl80211.c
@vknecht : I've seen your backporting work for the Xperia X. How does this work for Loire with SODP? Does e.g. a "set country code request" work for you, and if so, can you give me a hint?
I need some feedback from people with a Z3/Z3c/Z3Dual to see if the new builds work in affected countries, where 5GHz wifi is not working on current custom ROMs like e.g. LineageOS 17.1. I would appreciate if you test one of the builds below and send me a full log.
WARNING: The following builds are for debugging purpose only. Do not use them as a daily driver, as they have SELinux disabled and create excessive log entries. This ROM is not stable, some features are not yet implemented.
Xperia Z3 (D6603):
lineage-17.1-20201227-UNOFFICIAL-z3.zip
drive.google.com
Xperia Z3c (D5803):
lineage-17.1-20201227-UNOFFICIAL-z3c.zip
drive.google.com
Xperia Z3Dual (D6633) Update 10Jan2021:
lineage-17.1-20210110-UNOFFICIAL-z3dual.zip
drive.google.com
Z3Dual build has SELinux enabled already
If possible, please follow these steps:
Install ROM with TWRP for Android 10 or Lineage Recovery for 17.1
If possible, factory reset the device. Be sure to get rid of all former Magisk modules which try to set country codes etc. (if applicable).
Make sure a a local SIM card is inserted.
Boot the device. Enable mobile data and enable wifi. Connect to a 5GHz capable access point or router.
Optional: Increase log buffer size. This may be required as the kernel is set to verbose logging, creating large logfiles. You can do this via settings/developer options or via adb:
adb logcat -G 8M
Get close to the access point or router, so that the device would prefer 5GHz over 2.4GHz.
Reboot the device and let wifi connect. Check if device uses a 5Ghz connection. (Ignore bandwith / speed for now.)
Create a logfile, e.g. with this command via adb:
adb shell logcat -d -b all > mylog.log
The logfile may contain private information, so I recommend not to post them public. Together with the ligfile I would like to know
a) Wifi 5GHz working?
b) The country in which you have tested this.
nice work bro.
i live in iran and in this build my Z3 Dual detects wifi networks while the sim card is also connected.
but in 10 Jan 2021 update my phone can't detect my router's wifi unfortunately while the previous build could do it without problems.
hotspot turns on on both 2.4GHz and 5GHz.
in this new build cellular network and data are working.
Thanks @TheShadowOfAGhost20 !
Can you please run a root shell (E.g. by connecting via ADB, run adb root, then adb shell) and then
$> iw wlan0 scan → scan for networks
and then look if your access point is found?
Furthermore, can you please check which WiFi channel this particular router ist set to, and if possible the bandwidth?
Mr.Tom_Tom said:
Thanks @TheShadowOfAGhost20 !
Can you connect via ADB, run adb shell and then
$> iw wlan0 scan → scan for networks
and then look if your access point is found?
Furthermore, can you please check which WiFi channel this particular router ist set to, and if possible the bandwidth?
Click to expand...
Click to collapse
i did that but got this error: "/system/bin/sh: iw: inaccessible or not found"
but i found the cause: my wifi channel was set to 12. i changed it and then got detected!
TheShadowOfAGhost20 said:
i did that but got this error: "/system/bin/sh: iw: inaccessible or not found"
Click to expand...
Click to collapse
Sorry I forgot to write that you have to do this as root, I edited the post accordingly.
TheShadowOfAGhost20 said:
i found the cause: my wifi channel was set to 12. i changed it and then got detected!
Click to expand...
Click to collapse
Tha sounds reasonable. However, Channel 12 should be usable in IR.
Mr.Tom_Tom said:
Sorry I forgot to write that you have to do this as root, I edited the post accordingly.
Tha sounds reasonable. However, Channel 12 should be usable in IR.
Click to expand...
Click to collapse
channel 13 has detection problem too. the others are OK
.sorry erroneous post
New buildsFeedbacks have been positive so far, so here are some updated builds.
Lineage Sources* as of 20 March 2021
Kernel sources* based on Linux 3.4.113 with backported wifi from 5.8.18 plus cherry-pick of the following changes:
bluetooth: fixed #ifdef'ed PM callbacks ("BTLowPower" wakelock) 50f16d16b32871c5ce97b029e68692008c848bb2
SELinux enforcing
Build as userdebug, normal loglevels
* For links to sources see 1st post. Z3Dual does not have official Lineage17.1 sources yet, bringup is in progress.
Xperia Z3 (D6603):
HiDrive
hidrive.ionos.com
md5: d7aaf1fea120df3e2aad10b3a2d32226
Xperia Z3c (D5803):
HiDrive
hidrive.ionos.com
md5: 456ff87441c3a63e8dc8c7a8d03bdf39
Xperia Z3Dual (D6633):
HiDrive
hidrive.ionos.com
md5: 1848681c82d608f3212f1ace621327cb
As always, feedback is welcome.
Has anyone found a bug/installed this latest build yet? lineage-17.1-20210320-UNOFFICIAL-z3dual
Finding this super stable.. The only thing that does not work for me is the advanced boot recovery that goes back into system, But that's a known issue.
Mr.Tom_Tom said:
New buildsFeedbacks have been positive so far, so here are some updated builds.
Lineage Sources* as of 20 March 2021
Kernel sources* based on Linux 3.4.113 with backported wifi from 5.8.18 plus cherry-pick of the following changes:
bluetooth: fixed #ifdef'ed PM callbacks ("BTLowPower" wakelock) 50f16d16b32871c5ce97b029e68692008c848bb2
SELinux enforcing
Build as userdebug, normal loglevels
* For links to sources see 1st post. Z3Dual does not have official Lineage17.1 sources yet, bringup is in progress.
Xperia Z3 (D6603):
HiDrive
hidrive.ionos.com
md5: d7aaf1fea120df3e2aad10b3a2d32226
Xperia Z3c (D5803):
HiDrive
hidrive.ionos.com
md5: 456ff87441c3a63e8dc8c7a8d03bdf39
Xperia Z3Dual (D6633):
HiDrive
hidrive.ionos.com
md5: 1848681c82d608f3212f1ace621327cb
As always, feedback is welcome.
Click to expand...
Click to collapse
hi mr.tom. it's perfect as always, found no bug except wifi signal power, it's weak compared to stock roms but there was no difference in speeds. maybe it's because of wifi icon that shows little weaker signal.
and about overheating: i didn't test this build for long but while working with it i have noticed that my device is cooler than previous builds, maybe it's because of this new kernel.
i have recorded 4k for about 7 minutes then my phone rebooted i think that was because of too much heat, then i've reinstalled stock rom, however, stock rom's camera won't let me record much and the app shuts down because of heat, so i can't find out if stock rom can record 4k at least without rebooting.
i need to test this build for more time i hope the heating is now gone
and one question: can you port cyberian camera mod for these roms? or is that possible?
netwave said:
Has anyone found a bug/installed this latest build yet? lineage-17.1-20210320-UNOFFICIAL-z3dual
Finding this super stable.. The only thing that does not work for me is the advanced boot recovery that goes back into system, But that's a known issue.
Click to expand...
Click to collapse
lineage os recoveries have these problems yet, there's no fix for that, only the developer can fix it. currently the twrp works if you flash it to FOTAKernel partition but i think the twrp is useless because it doesn't install these builds.
Surely better to do: fastboot boot recovery-20201012-TESTING-z3dual.img rather than a "flash" recovery. What would be the point in flashing a recovery if its not working.
Hey
Thanks @Mr.Tom_Tom for new build and @TheShadowOfAGhost20 for testing dev builds!
today i installed the new release
but i have some problems with recovery and boot
after installing Lineage i cannot boot to recovery again
i tried adb, android advanced boot options and "fastboot boot image.img"
none of them taken me to recovery mode
so i needed to install Magisk , OpenGApps , and rom itself with adb sideload and reboot to system because i can't boot to recovery again
i'm now installing my apps for daily usage testing - i need about one or two week to test and use and see if anything is wrong or not
for now WiFi problem is gone , i have full wifi access and both sims antenna
again , thanks to everyone puts effort on this project (and sorry for bad English)
i will update this post if i found anything
navidmafi said:
today i installed the new release
but i have some problems with recovery and boot
after installing Lineage i cannot boot to recovery again
i tried adb, android advanced boot options and "fastboot boot image.img"
none of them taken me to recovery mode
Click to expand...
Click to collapse
If your going to settings\system\developer options\advanced restart\power\restart recovery , Forget it! this method doesn't work for now, & will only boot you back into Lineage. It's an issue that hopefully get's fixed in the future.
But here's a better way of entering recovery without having to flash it...
Check all your drivers are installed correctly & make sure you have the correct recovery to hand.
Here's what I Command:
adb devices
adb reboot bootloader
fastboot devices
fastboot boot recovery-20201012-TESTING-z3dual.img
Good luck!
Hey again
Thanks to @netwave i can now boot to recovery without problems by going to fastboot from adb , and booting image directly by "fastboot boot"
while using devices after installing new release , i have a problem with WiFi connectivity
when i lock the screen by power button , the wifi disconnects
for example i use whatsapp a lot and when screen is locked wifi is not connected
i checked power settings - and even set the battery profile to "Quick" (and battery saver is off) but it did not help
is this a bug or a feature?
navidmafi said:
Hey again
Thanks to @netwave i can now boot to recovery without problems by going to fastboot from adb , and booting image directly by "fastboot boot"
while using devices after installing new release , i have a problem with WiFi connectivity
when i lock the screen by power button , the wifi disconnects
for example i use whatsapp a lot and when screen is locked wifi is not connected
i checked power settings - and even set the battery profile to "Quick" (and battery saver is off) but it did not help
is this a bug or a feature?
Click to expand...
Click to collapse
Have you tried without Magisk installed? Don't use v22.0 what ever you do as it disables WiFi
Ow
I'm using Magisk and it is version 22.0
and even root not works
should i reflash ?
Edit : Ok i'm flashing again now
navidmafi said:
Ow
I'm using Magisk and it is version 22.0
and even root not works
should i reflash ?
Click to expand...
Click to collapse
Install the Magisk uninstall.zip from recovery
when your back in Lineage your still have a disabled WiFi as Magisk does not uninstall correctly.
So Install the original boot extracted from the Lineage.zip to get things working again.
- adb devices
- adb reboot bootloader
- fastboot devices
- fastboot flash boot boot.img
- fastboot reboot
Then your be sorted.
I guess I finally hard-bricked my N920P trying to install Universal SafetyNet Fix. It was on stock (N920PVPS3DRH1) but I had TWRP and Magisk Canary installed. I was trying to get Zygisk working but couldn't get it properly turn on, even on the stable and canary builds. That's where I had tried to install the SafetyNet fix module. It said it doesn't fully support anything below Android 8.0, but it did finish installing and asked me to reboot. And it never turned back on.
I cannot get into the download mode, recovery or system. Tried all key combos and no life at all. I drained the battery all night long and tried plugging into the PC and now it detects it as an unknown "Exynos7420" device. That was something from the nothing I got before. I tried looking up on how to rebuild the corrupt bootloader but I couldn't wrap my head around on how the process works. There was material on getting a software called "USB_Downloader" and I got all the way to installing the drivers and getting that software recognise the device as a COM port. I did this in a Windows 7 32 bit VM on VirtualBox (VMWare kept crashing my entire USB Host Controller everytime I tried passing the phone's connection to the VM, which was weird).
Now I'm stuck with this software and am unable to understand what I need to do next. There was something about getting the sboot.bin file and creating 4 new files to push through the Exynos COM port to fix the bootloader. There was also something about getting a Hex editor to do this, but I cannot understand what's going on. Could someone please help me get around this?
Thanks in advance!!
Never mind I fixed it. Just posting it here to make sure no one else gets stuck like I did for a long while. So what I had done was I forgot I had a custom ROM installed. It had been based on the N920PVPU3DQC5 firmware. So I downloaded that firmware, extracted the sboot.bin file then went to work with a hex editor (HxD for Windows specifically).
Open sboot.bin in the hex editor and start making new files listed below. The sections are also listed below, you can ensure the size in the bottom of HxD.
Save them as novi1.bin, novi_2.bin, etc...
The offsets I used are:
BL1 or novi1.bin: 0 - 0x1FFF (size 0x2000)
BL2 or EL3 or novi_2.bin: 0x2000 - 0x31FFF (size 0x30000)
EL3 or BL2 or novi_3.bin: 0x32000 - 0x3dfff (size 0xC000)
S-BOOT or novi_4.bin: 0x3E000 - 0x18F100 or end of file (size 0x15110), this will include tzsw.
Next this is the cfg file I used:
Code:
; S Project
; must keep order of binary list
; BL1
DNW_STORE e5250 fwbl1 200 20 novi1.bin
;DNW_WAIT
; BL2
DNW_STORE e5250 el3_mon 2000 20 novi_2.bin
; u-boot
; Wait Re-Enumeration
DNW_WAIT
DNW_STORE e5250 bl2 2000 20 novi_3.bin
;DNW_WAIT
DNW_STORE e5250 bootloader 20000 20 novi4.bin
;DNW_WAIT
;DNW_STORE e5250 tzsw 20000 20 4pt.img
Copy this code and save it as SH-usb-booting.cfg in the same folder as your .bin files. Now you can launch the multidownloader and load the .cfg and select Auto Run. Now press and hold the power button on your phone and connect it to the PC. It should automatically go through the whole flashing process and end up in the download mode screen. You can now flash the firmware from there!
If you have any doubts hit me up!
LOL I'm stuck again. I got into Download mode but my VM was having trouble connecting to the Download mode USB modem and it crashed the USB controller on my PC. I had to reboot the phone and now I'm stuck again in Exynos USB mode. Trying to get back into Download mode using the files I created above but it's not working anymore. I can hear the USB getting disconnected on the host at the AP Re-enumeration step but it isn't disconnecting from the guest VM. I guess I'll have to find a physical PC to try this out on.
EDIT: I had used VirtualBox until this step. After the hanging on Re-enumeration issue, I figured it could be Virtualbox causing the issue so I tried using VMWare, and ta-da, it worked. Read posts below for updates.
So I somehow got myself to get into Download mode consistently. Turned out my VM's USB controller was acting up so I clean installed it and I'm able to send the sboot files and get into Odin mode. But new trouble. Everytime I flash the stock firmware it goes through the process, passes and resets. But it never boots!! Just goes back to the same Exynos mode. I can re-flash the sboot file to get back into Odin mode but I'm stuck like this. I have no idea what to do now...
Progress so far:
I can't remember what custom ROM I had originally. Radeonmaya S8+ N920P ROM was supposed to be based on the DQC5 deodexed stock ROM posted here in the N920P forum.
1. Tried creating new files from DQC5 - SPR sboot.bin: Booted into Download mode, tried flashing the 4 file firmware, no progress, resets back into Exynos mode.
2. Used the DQC5 - SPR sboot.bin to boot into download mode: Tried flashing thr 4 file firmware for the latest firmware that was installed in the phone which was DRH1. No progress, resets back into Exynos mode.
If I'm reading this correctly, the Radeommaya ROM makes changes to boot.img and system partitions. Everything else remains stock, therefore my original bootloader for firmware DRH1 should work. However, I'm not able to get into the system.
I must note that TWRP recovery was installed on the device. The best course of action would be to install the same custom ROM back together with TWRP, but I could not find an Odin flashable tarball for the Radeonmaya ROM. The forum's been dead for a couple of years and the Telegram group is also dead. Looking for ways to make my own tarball using handpicked files maybe.
Currently trying to create new .bin files to boot into Download mode via the Multidownloader from sboot.bin files I salvaged from the XAS (Sprint Unbranded) firmware packages DRH1 and DQE1 (Apparently this firmware has helped someone in the Radeonmaya ROM thread to boot back into the system from a similar hard bricked situation, however I speculate this would not fix my problem because the DQE1 firmware is newer than the DQC1 firmware, which the custom ROM was based upon)
Will post more findings later.
P.S. VMWare could be quite finicky to work with when trying to passthrough the Exynos USB Device to a Windows 7 guest. It caused my AMD Ryzen host to crash its entire USB controller and both my USB mouse and the phone wouldn't connect to the HOST, let alone the guest. It causes a never-ending loop in the code which also stops a proper system restart, hence needing you to force power-cycle the whole computer.
This is because of the unusual nature of the driver being 32-bit only and incompatibility with VMWare. However, it should work when you reinstall VMWare without the Enhanced Keyboard driver, and also reinstalling the Exynos USB driver on the host and the VMWare USB Device (found in the Universal Serial Bus controllers section when you have the USB connection passed through to the VM).