Related
Ok, so I'm very new to rooting, Custom Firmware, all of it. I decided to try to root my Kindle Fire. I got CyanogenMod on it, but now it won't connect to the computer. I want to get it back to the normal Kindle Fire OS. Please Help!
ActorfromMI said:
Ok, so I'm very new to rooting, Custom Firmware, all of it. I decided to try to root my Kindle Fire. I got CyanogenMod on it, but now it won't connect to the computer. I want to get it back to the normal Kindle Fire OS. Please Help!
Click to expand...
Click to collapse
Hello there! First a warning, this method will remove root access FFF and TWRP (Everything) so if you don't want that, this is not the method for you.
First you want to download the stock kindle rom http://www.amazon.com/gp/help/customer/display.html/ref=hp_navbox_kspot_fireupdate?nodeId=200790620
And then just follow the steps on this post from another XDA member - http://forum.xda-developers.com/showthread.php?t=1399072
And you should be good
EDIT - Wait do you mean you can't connect to computer with a usb, or internet or what?
JakeReis said:
Hello there! First a warning, this method will remove root access FFF and TWRP (Everything) so if you don't want that, this is not the method for you.
First you want to download the stock kindle rom http://www.amazon.com/gp/help/customer/display.html/ref=hp_navbox_kspot_fireupdate?nodeId=200790620
And then just follow the steps on this post from another XDA member - http://forum.xda-developers.com/showthread.php?t=1399072
And you should be good
EDIT - Wait do you mean you can't connect to computer with a usb, or internet or what?
Click to expand...
Click to collapse
I cannot connect my kindle to the computer via usb. I tried downloading the stock rom to the kindle itself, and TWRP cant find it.
ActorfromMI said:
I cannot connect my kindle to the computer via usb. I tried downloading the stock rom to the kindle itself, and TWRP cant find it.
Click to expand...
Click to collapse
Ok thanks. Just to clarify, roms should be still zipped (so file extension should be .zip) and placed in the main SD card directory. So if your browser is downloading it to another place you should probably move it.
JakeReis said:
Ok thanks. Just to clarify, roms should be still zipped (so file extension should be .zip) and placed in the main SD card directory. So if your browser is downloading it to another place you should probably move it.
Click to expand...
Click to collapse
so how do i do this from the kindle alone?
ActorfromMI said:
so how do i do this from the kindle alone?
Click to expand...
Click to collapse
Step 1) Download ROM from link provided.
Step 2) Download a file manager like ES file Manager, although if you are on CM you should have one already.
Step 3) Use the File Manager to move the file from download to your root of the sdcard, which is /storage/sdcard/
Step 4) Make sure its zip file. Sometimes you may download a bin file, and it won't work. Rename to .zip if its a .bin
Step 5) Go to TWRP and first wipe System, Data, Dalvik and Cache ONLY. Install the the zip file.
Step 6) Reboot
It may take 1-3 Minutes before you enter the Original OS, please note that you WILL LOSE ROOT, FFF, TWRP.
Sent from my Amazon Kindle Fire using Tapatalk 4
404-Not Found said:
Step 1) Download ROM from link provided.
Step 2) Download a file manager like ES file Manager, although if you are on CM you should have one already.
Step 3) Use the File Manager to move the file from download to your root of the sdcard, which is /storage/sdcard/
Step 4) Make sure its zip file. Sometimes you may download a bin file, and it won't work. Rename to .zip if its a .bin
Step 5) Go to TWRP and first wipe System, Data, Dalvik and Cache ONLY. Install the the zip file.
Step 6) Reboot
It may take 1-3 Minutes before you enter the Original OS, please note that you WILL LOSE ROOT, FFF, TWRP.
Sent from my Amazon Kindle Fire using Tapatalk 4
Click to expand...
Click to collapse
I followed every step, and when i tried to install, I received this dialog:
Skipping MD5 check: no MD5 file found.
assert failed: getprop("ro.product.device") == "blaze" l l
E: unknown command [err_string]
getprop("ro.build.product") == "blaze"
E: unknown command [err_string]
E: Error executing updater binary in zip '/sdcard/update-kindle-6.3.2_D01E_4110520.zip'
Error flashing zip '/sdcard/update-kindle-6.3.2_D01E_4110520.zip'
Updating partition details
I then went to Reboot System, and it said:
No OS Installed! Are you
sure you wish to reboot?
There was no other option, so I had to. Now, I dont even have CyanogenMod. I let it sit on Booting... for 15 minutes and nothing.
ActorfromMI said:
I followed every step, and when i tried to install, I received this dialog:
Skipping MD5 check: no MD5 file found.
assert failed: getprop("ro.product.device") == "blaze" l l
E: unknown command [err_string]
getprop("ro.build.product") == "blaze"
E: unknown command [err_string]
E: Error executing updater binary in zip '/sdcard/update-kindle-6.3.2_D01E_4110520.zip'
Error flashing zip '/sdcard/update-kindle-6.3.2_D01E_4110520.zip'
Updating partition details
I then went to Reboot System, and it said:
No OS Installed! Are you
sure you wish to reboot?
There was no other option, so I had to. Now, I dont even have CyanogenMod. I let it sit on Booting... for 15 minutes and nothing.
Click to expand...
Click to collapse
Well, here is a thread I found that mentions the error (about 3/4's of the way down the page), and a potential fix someone had. Unfortunately it requires you to be able to connect your kindle to the computer to use kindle fire utility to work. Will it connect to kindle fire utility, or is that not working either?
http://androidforums.com/kindle-fir...474455-restore-kindle-fire-out-box-state.html
JakeReis said:
Well, here is a thread I found that mentions the error (about 3/4's of the way down the page), and a potential fix someone had. Unfortunately it requires you to be able to connect your kindle to the computer to use kindle fire utility to work. Will it connect to kindle fire utility, or is that not working either?
Click to expand...
Click to collapse
When I try to connect to the kindle fire utility, it says offline.
ActorfromMI said:
When I try to connect to the kindle fire utility, it says offline.
Click to expand...
Click to collapse
I'm running out of ideas, but is it possible to reflash CM? If you can, then there is still another way. You could download another rom directly from your device (like glazed ics for example) flash it, and then you could connect it to a computer to continue. I just flashed glazed ics today and it connects to hte computer with my old cell phone cable, so it should work for you.
JakeReis said:
I'm running out of ideas, but is it possible to reflash CM? If you can, then there is still another way. You could download another rom directly from your device (like glazed ics for example) flash it, and then you could connect it to a computer to continue. I just flashed glazed ics today and it connects to hte computer with my old cell phone cable, so it should work for you.
Click to expand...
Click to collapse
CM is not working, after trying to install the stock ROM. All I can do now is get to TWRP.
I dont how if this will give any more help, but I just tried it again, and there was a page I forgot to say. After i go to reboot, and it gives me the warning about no OS installed, it then asks me if I want to install SuperSU, and it says my device doesn't appear to be rooted. I hope someone can give me a solution to this, it is beyond frustrating.
ActorfromMI said:
I dont how if this will give any more help, but I just tried it again, and there was a page I forgot to say. After i go to reboot, and it gives me the warning about no OS installed, it then asks me if I want to install SuperSU, and it says my device doesn't appear to be rooted. I hope someone can give me a solution to this, it is beyond frustrating.
Click to expand...
Click to collapse
anyone???
ActorfromMI said:
anyone???
Click to expand...
Click to collapse
There is a "Mount" function in TWRP. See if it will let you mount your sdcard to USB and transfer a ROM to it.
soupmagnet said:
There is a "Mount" function in TWRP. See if it will let you mount your sdcard to USB and transfer a ROM to it.
Click to expand...
Click to collapse
nope. nothing.
ActorfromMI said:
nope. nothing.
Click to expand...
Click to collapse
As annoying as it is, your communication problem may be due to the drivers not being installed correctly. You may want to check your device manager to see if everything is connected. Furthermore, if you have access to your current OS, you may want to check the Developer Options, and confirm that you have debugging enabled. Depending on the drivers you installed to get ADB working, it is entirely possible that you could be able to communicate with the device while booted normally, but not in recovery.
If nothing else, TWRP should have a command line tool where you can perform simple tasks like renaming files from within recovery, and without the need for an ADB connection. You might want to look into that to see if you can find the 'update.bin' that you downloaded to your device (likely located in your "Download" folder), and rename it to 'update.zip' so it will be visible to TWRP for flashing (that is, assuming you really want to revert to stock).
soupmagnet said:
As annoying as it is, your communication problem may be due to the drivers not being installed correctly. You may want to check your device manager to see if everything is connected. Furthermore, if you have access to your current OS, you may want to check the Developer Options, and confirm that you have debugging enabled. Depending on the drivers you installed to get ADB working, it is entirely possible that you could be able to communicate with the device while booted normally, but not in recovery.
If nothing else, TWRP should have a command line tool where you can perform simple tasks like renaming files from within recovery, and without the need for an ADB connection. You might want to look into that to see if you can find the 'update.bin' that you downloaded to your device (likely located in your "Download" folder), and rename it to 'update.zip' so it will be visible to TWRP for flashing (that is, assuming you really want to revert to stock).
Click to expand...
Click to collapse
It recognizes the update, it just won't work
Hi.So I used to have Cyanogenmod installed on my rooted Kindle Fire, along with FFF and TWRP recovery. I was not satisfied with the performance of Cyangogenmod, so I wanted to install the Stock Amazon ROM back onto the Fire. First, I booted into TWRP, and erased everything with the 'wipe' option (might not have been a good idea). I have downloaded the Amazon ROM from here: http://kindle-fire-updates.s3.amazonaws.com/update-kindle-6.3_D01E_4019920.bin, and renamed the file 'update.zip'. I mount the Fire, and drag over the update.zip, and then I go to 'install' in TWRP and select the update.zip, but after I start it, the install just fails, seconds after it's started. There are a couple errors, such as "Error executing updater binary in zip '/sdcard/update.zip'". I have ADB installed, and Kindle Fire Utility, which detects the device as 'online', boot status 4000. I have tried install COTR recovery with KFU, but it hangs at 'Activating Fastboot (4002)'. I would really appreciate any help with this, because it would really suck if it turns out that I bricked my Fire. Thanks!
Also having trouble taking my KF back to factory...
I am also having trouble taking my KF back to factory specs.
I am using TWRP recovery.
Wipes go just fine.
Install gives me this error...
Skipping MD5 check: no MD5 file found.
assert failed: getprop ("ro.product.device") == "blaze" ||
E:unknown command [err_string]
getprop("ro.build.product") == "blaze"
E:unknown command [err_string]
E:Error executing updater binary in zip '/sdcard/kindle/update.zip'
Error flashing zip '/sdcard/kindle/update.zip'
Updating partition details...
I am trying to go back to stock because I am now having TONS of trouble keeping files running without them crashing. Also, every time I try to read a book now, the Kindle app crashes before it ever really opens. I have tried uninstalling that app, then reinstalling even. No help at all.
Any help in this matter would be HUGELY APPRECIATED!!!!
Thanks,
me
BriteLeaf said:
I am also having trouble taking my KF back to factory specs.
I am using TWRP recovery.
Wipes go just fine.
Install gives me this error...
Skipping MD5 check: no MD5 file found.
assert failed: getprop ("ro.product.device") == "blaze" ||
E:unknown command [err_string]
getprop("ro.build.product") == "blaze"
E:unknown command [err_string]
E:Error executing updater binary in zip '/sdcard/kindle/update.zip'
Error flashing zip '/sdcard/kindle/update.zip'
Updating partition details...
I am trying to go back to stock because I am now having TONS of trouble keeping files running without them crashing. Also, every time I try to read a book now, the Kindle app crashes before it ever really opens. I have tried uninstalling that app, then reinstalling even. No help at all.
Any help in this matter would be HUGELY APPRECIATED!!!!
Thanks,
me
Click to expand...
Click to collapse
Yes I am getting almost the exact same error. I would really like a solution to this.
Ethanzh said:
Yes I am getting almost the exact same error. I would really like a solution to this.
Click to expand...
Click to collapse
So would I. I am glad that I am not the only one.
I am guessing...
I am guessing either us 3 are the only ones with this problem, or just no one wants to, or knows how to fix this problem =(
If a flash does not complete, it has to be a bad download. Get the file again and push it to the sdcard via twrp. But if you are having trouble, why flash factory? If it is some corruption, flash a rom. Kindle store and reader fail because of the app, generally. Notice my device says Nexus 7? That is how to fool the kindle apps on a fully functioning kindle fire.
Sent from my Nexus 7 using xda app-developers app
Ixthusdan said:
If a flash does not complete, it has to be a bad download. Get the file again and push it to the sdcard via twrp. But if you are having trouble, why flash factory? If it is some corruption, flash a rom. Kindle store and reader fail because of the app, generally. Notice my device says Nexus 7? That is how to fool the kindle apps on a fully functioning kindle fire.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I have redownloaded the flash from Amazon at least five times, all with the same results.
As far as pushing it to the sdcard via twrp, I guess I for one don't know how to do that.
As to why I would want to go back to factory with it, I guess for me, it is what I prefer.
Thank you for answering though. I do appreciate it.
Same here, fixed!
Ethanzh said:
Hi.So I used to have Cyanogenmod installed on my rooted Kindle Fire, along with FFF and TWRP recovery. I was not satisfied with the performance of Cyangogenmod, so I wanted to install the Stock Amazon ROM back onto the Fire. First, I booted into TWRP, and erased everything with the 'wipe' option (might not have been a good idea). I have downloaded the Amazon ROM from here: , and renamed the file 'update.zip'. I mount the Fire, and drag over the update.zip, and then I go to 'install' in TWRP and select the update.zip, but after I start it, the install just fails, seconds after it's started. There are a couple errors, such as "Error executing updater binary in zip '/sdcard/update.zip'". I have ADB installed, and Kindle Fire Utility, which detects the device as 'online', boot status 4000. I have tried install COTR recovery with KFU, but it hangs at 'Activating Fastboot (4002)'. I would really appreciate any help with this, because it would really suck if it turns out that I bricked my Fire. Thanks!
Click to expand...
Click to collapse
I had the same problem. I ended up reverting back to TWRP 2.2.2.1, which can read the update.zip properly.
I downloaded the older version from techerrata dot com --> twrp2 -->blaze-->openrecovery-twrp-2.2.2.1-blaze.img
I then used my fastboot cable and ran fastboot -i 0x1949 boot openrecovery-twrp-2.2.2.1-blaze.img.
This allowed me to run the older twrp, clear out my /system, and get back to stock.
mpeterso said:
I had the same problem. I ended up reverting back to TWRP 2.2.2.1, which can read the update.zip properly.
I downloaded the older version from techerrata dot com --> twrp2 -->blaze-->openrecovery-twrp-2.2.2.1-blaze.img
I then used my fastboot cable and ran fastboot -i 0x1949 boot openrecovery-twrp-2.2.2.1-blaze.img.
This allowed me to run the older twrp, clear out my /system, and get back to stock.
Click to expand...
Click to collapse
Thanks, trying this now.
TWRP 2.2.2.1 Worked
mpeterso said:
I had the same problem. I ended up reverting back to TWRP 2.2.2.1, which can read the update.zip properly.
I downloaded the older version from techerrata dot com --> twrp2 -->blaze-->openrecovery-twrp-2.2.2.1-blaze.img
I then used my fastboot cable and ran fastboot -i 0x1949 boot openrecovery-twrp-2.2.2.1-blaze.img.
This allowed me to run the older twrp, clear out my /system, and get back to stock.
Click to expand...
Click to collapse
Thanks for the tip. Worked like a champ.
mpeterso said:
I had the same problem. I ended up reverting back to TWRP 2.2.2.1, which can read the update.zip properly.
I downloaded the older version from techerrata dot com --> twrp2 -->blaze-->openrecovery-twrp-2.2.2.1-blaze.img
I then used my fastboot cable and ran fastboot -i 0x1949 boot openrecovery-twrp-2.2.2.1-blaze.img.
This allowed me to run the older twrp, clear out my /system, and get back to stock.
Click to expand...
Click to collapse
I just get stuck at < waiting for device > on my command prompt. Where am I supposed to open the cmd?
I just wanted to say, after several hours of searching through Google and messing with my Kindle, this thread finally helped me fix it.
My biggest issue was, I was unable to flash any thing, even the twrp. So what I had to do was this,
I googled the twrp 2.2.2.1 blaze img as mentioned here, then I renamed it to twrp.img and put it in the folder inside KFU -> Recovery
My other issue was with my Kindle being stuck at the Boot Logo saying, "Booting" and I noticed through trial and error, before the kindle goes to try to boot (When you can select Normal, Recovery, Reset Boot) that if I kept pressing the power button to cycle through the options, I could keep the Kindle in a Fastboot mode so I could use the KFU to install the TWRP 2.2.2.1
After that it was simple, booted into twrp, mounted the drive and stuck the Stock Rom from Amazon on there and installed it.
So I really just wanted to say thank you to this thread and hopefully I can contribute a small bit to someone if they have my issue.
Bump
Having the exact same issue when using KFU it just hangs there on activating fast boot
Cronus3166 said:
I just wanted to say, after several hours of searching through Google and messing with my Kindle, this thread finally helped me fix it.
My biggest issue was, I was unable to flash any thing, even the twrp. So what I had to do was this,
I googled the twrp 2.2.2.1 blaze img as mentioned here, then I renamed it to twrp.img and put it in the folder inside KFU -> Recovery
My other issue was with my Kindle being stuck at the Boot Logo saying, "Booting" and I noticed through trial and error, before the kindle goes to try to boot (When you can select Normal, Recovery, Reset Boot) that if I kept pressing the power button to cycle through the options, I could keep the Kindle in a Fastboot mode so I could use the KFU to install the TWRP 2.2.2.1
After that it was simple, booted into twrp, mounted the drive and stuck the Stock Rom from Amazon on there and installed it.
So I really just wanted to say thank you to this thread and hopefully I can contribute a small bit to someone if they have my issue.
Click to expand...
Click to collapse
This worked perfectly for me. Felt a little weird sitting there repeatedly pressing the power button as KFU searched for my device, but it worked. Thanks.
Hallo,
i bricked my Ouya. I have CWM installed. I started my Ouya and get a Update, then I rebooted in Recovery an I stock there. I took my Keyboard, powered OUYA of, restarted without Ethernet and rebootet to recovry.
Then i format the /system to get rid of mod-Collection. Then i want to install update.zip, but it wasen´t there. Now I have a Ouya only with CWM.
CWM did not find my USB-Stick. And when i connect my Laptop to the Ouya I can not find a USB-Memory. My Ouya-Driver did not recocnize the Ouya!
But the i a topic in CWM load from Sideloading! How can I put a *-ota.zip an the OUYA to flash system angain?
Thanks.
gueschmid
DONE!
I FOUND ADB SIDELOAD *-OTA.ZIP
gueschmid said:
Hallo,
i bricked my Ouya. I have CWM installed. I started my Ouya and get a Update, then I rebooted in Recovery an I stock there. I took my Keyboard, powered OUYA of, restarted without Ethernet and rebootet to recovry.
Then i format the /system to get rid of mod-Collection. Then i want to install update.zip, but it wasen´t there. Now I have a Ouya only with CWM.
CWM did not find my USB-Stick. And when i connect my Laptop to the Ouya I can not find a USB-Memory. My Ouya-Driver did not recocnize the Ouya!
But the i a topic in CWM load from Sideloading! How can I put a *-ota.zip an the OUYA to flash system angain?
Thanks.
gueschmid
DONE!
I FOUND ADB SIDELOAD *-OTA.ZIP
Click to expand...
Click to collapse
If anyone has this problem in the future, you could use sideload or you could just adb push ie.
adb push update.zip /sdcard/update.zip
prophetjinn said:
If anyone has this problem in the future, you could use sideload or you could just adb push ie.
adb push update.zip /sdcard/update.zip
Click to expand...
Click to collapse
I did it this way all the time. But now it doesn't seem to work anymore.
I flashed the latest update I downloaded from https://ouyafw.skumler.net/
and getting this error when applying the update.zip from SDK or sideloading it (both doesn't work)
Code:
assert failed: !less_than_int(1391471878, getprop("ro.build.date.utc"))
I tried removing this line from the updater-script. Doesn't work. The progress stops with "Installation aborted." without an error code.
seems with further firmwares, there is no way to restore anymore.
PS: I don't have CWM. only Stock recovery and a system that stucks in bootloop even after factory reset.
nex86 said:
I did it this way all the time. But now it doesn't seem to work anymore.
I flashed the latest update I downloaded from https://ouyafw.skumler.net/
and getting this error when applying the update.zip from SDK or sideloading it (both doesn't work)
Code:
assert failed: !less_than_int(1391471878, getprop("ro.build.date.utc"))
I tried removing this line from the updater-script. Doesn't work. The progress stops with "Installation aborted." without an error code.
seems with further firmwares, there is no way to restore anymore.
PS: I don't have CWM. only Stock recovery and a system that stucks in bootloop even after factory reset.
Click to expand...
Click to collapse
The firmware on the site you mentioned is not up to date!
Here is the official link for the latest firmware.
If you have adb access, you could try to fastboot CWM recovery.
Can't install any ROMs on G2.
Had CWM 5.0.27, I think. Couldn't install any of several ROMs. Installed CWM 6.0.4.5. Same outcome.
Aroma installer always stops at "Symlinking..." after extracting files.
Says "set_perm: some changes failed" and Status 7.
What am I doing wrong?
O's said:
Can't install any ROMs on G2.
Had CWM 5.0.27, I think. Couldn't install any of several ROMs. Installed CWM 6.0.4.5. Same outcome.
Aroma installer always stops at "Symlinking..." after extracting files.
Says "set_perm: some changes failed" and Status 7.
What am I doing wrong?
Click to expand...
Click to collapse
Well as far as I remember, the new roms were better to be installed with 4ext Recovery, because the CWM had some problems working with ext4 filesystem. Try the one I have on the web site below, that should fix it for you.
a.s.j said:
Well as far as I remember, the new roms were better to be installed with 4ext Recovery, because the CWM had some problems working with ext4 filesystem. Try the one I have on the web site below, that should fix it for you.
Click to expand...
Click to collapse
Thanks, but the zip didn't work. Put it in sdcard root and tried several times with CWM Touch 5.8.1.0 -- installation failed, every time.
I've since gotten CM10.1 and Mimicry to work with CWM, but I'm struggling with one ROM in particular no matter the recovery: coolIOS, a 4.0.4.
Tried to install it with CWM 5.0.2.7 and got the error described at top.
Tried with CWM 6.0.4.5.
Tried with CWM Touch 5.8.1.0.
Tried with TWRP 2.6.3.0.
Same error, every time. Redownloaded the ROM, but same. I'm really at a loss with that one. It worked fine on a previous G2.
O's said:
Thanks, but the zip didn't work. Put it in sdcard root and tried several times with CWM Touch 5.8.1.0 -
Click to expand...
Click to collapse
Just try to install 4EXT recovery !
http://4ext.net/
Kéno40 said:
Just try to install 4EXT recovery !
http://4ext.net/
Click to expand...
Click to collapse
I meant the only 4ext install zip I could find didn't work.
Downloaded the apk from the site and got "Cannot open file".
Yes, Unknown Sources is checked.
Thanks, anyway.
EDIT: Got 4ext working, but still no help. Had to extract the .img from the install zip, install Mimicry ROM, and use the Terminal Emulator to flash the .img. That got it working, but it only boots in safe mode. Says it can't read the cache partition, and also says this:
"If you changed hboot you should choose to format all partitions (except sdcard)".
Formatted all partitions, rebooted recovery -- still safe mode. Still says it can't read cache.
Starting to think some of the physical memory is corrupt.
But if that's the case, why do other ROMs work? Or does someone else see another plan/fix/anything here? Thanks.
O's said:
I meant the only 4ext install zip I could find didn't work.
Downloaded the apk from the site and got "Cannot open file".
Yes, Unknown Sources is checked.
Thanks, anyway.
EDIT: Got 4ext working, but still no help. Had to extract the .img from the install zip, install Mimicry ROM, and use the Terminal Emulator to flash the .img. That got it working, but it only boots in safe mode. Says it can't read the cache partition, and also says this:
"If you changed hboot you should choose to format all partitions (except sdcard)".
Formatted all partitions, rebooted recovery -- still safe mode. Still says it can't read cache.
Starting to think some of the physical memory is corrupt.
But if that's the case, why do other ROMs work? Or does someone else see another plan/fix/anything here? Thanks.
Click to expand...
Click to collapse
There is no install zip on my pages, just zipped image which should be pushed in via Fastboot. You are perhaps doing something terribly wrong my friend.
What you need to do can be achieved by several ways:
- Rename recovery.zip to PC10IMG.zip put it into your /sdcard root and start your phone to recovery (hold Vol-Down and Power to start recovery system)
- use adb to push the image to the recovery partition
- or the easiest could be to check this one: http://www.4ext.net/install.pdf
a.s.j said:
There is no install zip on my pages, just zipped image which should be pushed in via Fastboot. You are perhaps doing something terribly wrong my friend.
What you need to do can be achieved by several ways:
- Rename recovery.zip to PC10IMG.zip put it into your /sdcard root and start your phone to recovery (hold Vol-Down and Power to start recovery system)
- use adb to push the image to the recovery partition
- or the easiest could be to check this one: http://www.4ext.net/install.pdf
Click to expand...
Click to collapse
Perhaps I was unclear. I downloaded your zip and renamed it PC10IMG.zip and put it in sdcard root and started to recovery, but that did not work. I thought it would work, since the phone showed the "vertical progress bar" as if it was about to change recovery, but I didn't get the prompt to "Update recovery?" that I usually see there. So nothing happened.
I also tried to download the 4ext apk directly from the site onto my phone, but after downloading the apk, phone said "Cannot open file."
Instead, I got 4ext working by downloading the zip in the 4ext forum zip. It contains an .img that I flashed in Terminal Emulator, which got 4ext working.
Once I booted to 4ext, it said it could only load in safe mode because it couldn't read the cache. It advised to wipe the cache, so I wiped everything several times, but it still only loads in safe mode.
I'll try your zip method again, and I thank you for the assistance. I just don't get why five different recoveries work on some ROMs but not one that worked fine on a past G2.
O's said:
Perhaps I was unclear. I downloaded your zip and renamed it PC10IMG.zip and put it in sdcard root and started to recovery, but that did not work. I thought it would work, since the phone showed the "vertical progress bar" as if it was about to change recovery, but I didn't get the prompt to "Update recovery?" that I usually see there. So nothing happened.
I also tried to download the 4ext apk directly from the site onto my phone, but after downloading the apk, phone said "Cannot open file."
Instead, I got 4ext working by downloading the zip in the 4ext forum zip. It contains an .img that I flashed in Terminal Emulator, which got 4ext working.
Once I booted to 4ext, it said it could only load in safe mode because it couldn't read the cache. It advised to wipe the cache, so I wiped everything several times, but it still only loads in safe mode.
I'll try your zip method again, and I thank you for the assistance. I just don't get why five different recoveries work on some ROMs but not one that worked fine on a past G2.
Click to expand...
Click to collapse
SOLVED: Helps if I read the instructions. Thread for that ROM clearly says to have Desire Z hboot; I had G2 hboot. In all the years of using a G2, I've never had to switch hboot and was unfamiliar with it. If anyone else has same issues as this post, might try installing the Virtuous Team's PC10IMG.zip and read up on it at the Hboot thread. Thanks to all who beared with my lack of knowledge.
Hello everyone!
My oneplus3 is actually running no OS and I'm having a boot loop.
I will try to explain what happened to me with the most details I can.
Before I ****ed everything up, I think I was running OxygenOS 3.28, not really sure about it but im 100% sure it was below 4.0, and it was rooted with TWRP 3.0.2 installed.
1) Today I had a pop up saying OxygenOS 4.0.2 was available (the official one that pops on the screen on boot) "Yay so coooool Nougat!"
1.1) I downloaded it, 1.4Go, then I pressed install
1.2) TWRP showed up, I didn't know what to do and that's where I ****ed up, I set my phone "factory new" in TWRP.
1.3) Phone restarted fresh new, I thought I had 4.0.2 but naaaaah would've been too easy so the official pop up showed again, I was still 3.28 I think.
1.4) Downloaded it once more, TWRP opened again, this time i was looking for the update i just downloaded in the "install" section. I browsed for quite a while and couldn't find it.
1.5) Master ****-up here: I tried to restore a backup. Then the bootloop happened. The black screen with "Oneplus" written in white. I was able to go back in TWRP by pressing power + volume down
1.6) Tried every kind of restore unsuccessfully, and tried ADB but it wouldn't load. Also TWRP said that I was running no OS when I wanted to turn off my phone for example.
2) I downloaded 4.0.2 from one plus website on my mac, and i flashed the official recovery instead of TWRP.
2.1) Transferred the update from my mac to my PC (seems important to me) and installed ADB & everything on both PC/O+3.
2.2) so adb worked in forceboot, i've been able to flash official recovery, tried once more to wipe & everything, but clearly I have no OS now, as TWRP said.
2.3) so i had the update in a folder (not a zip, probably due to the download being done from a mac), I made it a .ZIP with winrar, but "adb sideload update.zip" crashed at 0% everytime
2.4) looked at the archive then i noticed it was first a folder "OnePlus3Oxygen_16_OTA_039_all_1701140133_03b794d8a8b44883" then inside it i had the content like "boot.img" & everything. So i zipped it again but without that first folder because I thought it was the problem, but it kept on crashing 0%.
2.5) restarted my PC, looked on several forums, but i couldn't find any fix. Now adb can't even open update.zip anymore, it fails even before 0%.. I tried naming it .zip.zip, keeping the name "OnePlus3Oxygen_16_OTA_039_all_1701140133_03b794d8a8b44883.zip", using a third party app to allow more RAM to the cmd app...
I've been trying hard for 4 hours but I still have a O+3 without any OS... My last idea is downloading "OnePlus3Oxygen_16_OTA_039_all_1701140133_03b794d8a8b44883.zip" from my PC so it downloads it directly .zip unlike on my mac...
I hope I said everything, sorry for the long post but i'm desperate.. thanks for your attention,
Valentin
Try this guide: https://forum.xda-developers.com/oneplus-3/how-to/guide-flashing-oos-v4-0-1-custom-rom-t3537757
Let me know if it works.
EDIT: See FAQ #1, 2, 4, 12, 14 and 17.
dbabaev21 said:
Try this guide: https://forum.xda-developers.com/oneplus-3/how-to/guide-flashing-oos-v4-0-1-custom-rom-t3537757
Let me know if it works.
EDIT: See FAQ #1, 2, 4, 12, 14 and 17.
Click to expand...
Click to collapse
Thank you for answering! unfortunately i've already tried that and my problem occurs when i try to sideload the update from adb recovery... "couldn't load 'update.zip'"
I dont really know what to do now because I think my only option here is to load the OS through adb as I can't boot my phone to get the update zip inside a specified folder to load it from internal storage.
Try to install the new official TWRP version i think it is 3.0.3-0 through fastboot. Boot up TWRP, wipe every partiton and copy the update.zip onto the phone. You can copy it by connecting it normaly via USB(like you would do in OOS) and install the zip file afterwards.
Sleazy_ said:
Thank you for answering! unfortunately i've already tried that and my problem occurs when i try to sideload the update from adb recovery... "couldn't load 'update.zip'"
I dont really know what to do now because I think my only option here is to load the OS through adb as I can't boot my phone to get the update zip inside a specified folder to load it from internal storage.
Click to expand...
Click to collapse
install stock recovery and then try installing official OS. Or install modded twrp 3.0.2-1.28 and then try installing Freedom OS 2.3 via sideload or through internal storage.
Sleazy_ said:
Thank you for answering! unfortunately i've already tried that and my problem occurs when i try to sideload the update from adb recovery... "couldn't load 'update.zip'"
I dont really know what to do now because I think my only option here is to load the OS through adb as I can't boot my phone to get the update zip inside a specified folder to load it from internal storage.
Click to expand...
Click to collapse
Stop fiddling with the ROM. Download the ROM afresh directly to your Windows PC/laptop. Check the md5. Then start experimenting with the other suggestions but don't again meddle with the ROM!
Sleazy_ said:
Thank you for answering! unfortunately i've already tried that and my problem occurs when i try to sideload the update from adb recovery... "couldn't load 'update.zip'"
I dont really know what to do now because I think my only option here is to load the OS through adb as I can't boot my phone to get the update zip inside a specified folder to load it from internal storage.
Click to expand...
Click to collapse
I read your post again and here are a few things:
* Don't update Stock OOS via "System updates" in Settings if you are rooted and have TWRP
* Back up your data before updating, wiping or doing something with your phone.
* For the ADB error, see the FAQ #17 in the guide I provided.
Now, try this:
Flash TWRP via fastboot > boot to TWRP > connect your phone to your PC and copy the full Stock OOS v4.0.2 OTA to your phone > reboot to fastboot and flash Stock Recovery.
It didn't touch the internal storage. So, try to install from internal storage when you are in Stock Recovery.
Let me know if it worked.