Related
two days ago, i rooted my phone using simple root, nand unclocked and flashed clockwordmod and everything. i was using fresh rom, and i wanted to use the vanilla lockscreen. but in order to do that, i needed to flash amons ra. i tried doing that, and somehow i got rid of my clockword recovery mod (and amons ra didnt work) so whenever i went into recovery mode, it just stayed at the screen with the phone and triange and red exclamation mark. i tried running the recovery windows .bat file, but it didnt work. and i tried running the ruu .exe file to unroot my phone, but everytime it said it couldnt find my device, even though it was connected via a usb chord. i tried it in charge only mode, disk drive mode, and htc sync mode and none of them worked. i tried using rom manager, but everytime i tried doing something it said error attempting to run privilidged scrips or something. i tried downloading the superuser .apk file and installing it onto my phone, but that didnt work either. the terminal emulator didnt work when i tried to flash something, it just said it couldnt find the file on my sd card, even though i put it on there. help?
Okay, number one: Did you try holding volume UP + power at the red exclamation screen? I think that's how you enter AR recovery.
Number two: You can flash Fresh tweaks without using AR. You just have to reboot into ClockworkMod and flash the .zip files manually.
Are you able to boot ANY ROM right now? If so, is it rooted? If it is, try to reinstall ROM Manager.
Sounds like you went a little off the deep end when you couldn't get into AR.
any suggestions?
Yeah, answer my questions or provide more info so you can get better direction.
you can reflash either recovery with the simple root program or you can follow the first part of toasts root method part 2 to restore recovery.
SilverZero said:
Okay, number one: Did you try holding volume UP + power at the red exclamation screen? I think that's how you enter AR recovery.
Number two: You can flash Fresh tweaks without using AR. You just have to reboot into ClockworkMod and flash the .zip files manually.
Are you able to boot ANY ROM right now? If so, is it rooted? If it is, try to reinstall ROM Manager.
Sounds like you went a little off the deep end when you couldn't get into AR.
Click to expand...
Click to collapse
ill try your first suggestion. and i cant boot any rom right now, because rom manager isnt working. and im pretty sure my phone is rooted, because i still have dev tools and CIQ settings and all those rooted apps.
update: your first suggestion worked, except once i entered AR recovery, the only options i had were: reboot system now, apply sdcard:update.zip, wipe data/factory reset, and wipe cache partition. at the bottom, it said "E: can't open /cache/recovery/command,
t3project said:
you can reflash either recovery with the simple root program or you can follow the first part of toasts root method part 2 to restore recovery.
Click to expand...
Click to collapse
i tried reflashing with simple root but it didnt work. can you give me a link for toasts method?
i had a similar problem, i used the OTA simple root, get that and plug ur phone back in with debugging on , one of the drop down menus will let you flash a recovery so flash clockworkmod
okay so somehow i managed to unroot it by wiping my data/cache..but now whenever i try using simpleroot or OTA simpleroot it doesnt work, because it says device is not found. i have it plugged in via usb, usb debugging is on, and ive tried it in charge mode and disk drive mode. anyone know what the problem is?
I'm sure there is a way to fix this, but I would suggest using the full root method by toastcfh.
okay i'll just reroot using that method, thanks. also, whenever im on my computer and im using command prompt, none of the adb commands ever work. do i need to download something for it to work?
Yes, you need the ADB framework. Read the guide (or the one by TheBiles, which is basically a rewrite). The ADB framework is a part of the Android SDK. You have to run ADB commands from the ADB directory (which is actually the "tools" folder inside of the SDK directory, wherever you extract that). Just cd to the tools folder, then run your commands from there.
I rooted my Kindle Fire using KFU 0.9.5 and flashed a custom ROM. It worked fine for a few days and then just crashed -- The options bar located on the bottom disappeared and the error message was: System UI has crashed. (I have attached two pictures for better clarity)
Also, whenever I boot up, there is no yellow flame that appears, it goes to the moving colourful discs straight on.
I tried using terminal emulator and entered many codes in some hope of mounting USB Mass Storage so that I can use KFU and restore my Kindle, but in vain.
I have tried EVERYTHING. I've been at this for 6 days now and am at wits end. :crying: I have read up close to a 100 articles; this was my last resort.
I just want to get the Kindle's stock OS back - no root, nothing.
And the only was is, I suppose, if I am able to mount my Kindle as USB Mass Storage onto my computer.
ANY help is appreciated!
AndroBoss.
I don't have a kindle but did you try wiping it and reinstalling it?
Sent from my SPH-L710 using xda app-developers app
jr71x said:
I don't have a kindle but did you try wiping it and reinstalling it?
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
As it now runs on ICS, there is no Gingerbread for Kindle anymore on it. I can't wipe it clean from the device or atleast I don't know how to, please help?
All the wipes you should need to perform can be done in twrp recovery. Wipe factory reset , wipe cache , wipe dalvik and wipe the system. Reflash ROM , reflash gapps , reboot then system if prompted and you should be good to go.
Edit: failing to use the correct method to return to stock will just cause more problems. Rather than trying to go back to pure stock without fff and twrp I suggest you perform the above wipes and flash this instead http://forum.xda-developers.com/showthread.php?t=1439916 its just modified stock with Google play and it will not wipe out your recovery and bootloader.
Thepooch said:
All the wipes you should need to perform can be done in twrp recovery. Wipe factory reset , wipe cache , wipe dalvik and wipe the system. Reflash ROM , reflash gapps , reboot then system if prompted and you should be good to go.
Edit: failing to use the correct method to return to stock will just cause more problems. Rather than trying to go back to pure stock without fff and twrp I suggest you perform the above wipes and flash this instead http://forum.xda-developers.com/showthread.php?t=1439916 its just modified stock with Google play and it will not wipe out your recovery and bootloader.
Click to expand...
Click to collapse
Okay, I will flash what you suggested but that's the problem. I am unable to access TWRP recovery from my Kindle. When it boots up there is no yellow flame that appears as the custom ROM is ICS 4.0.
I tried mounting a twrp.img on to the SD Card after downloading one straight onto the tab but of no avail :/
What do you suggest? Is there any way I can get the TWRP Recovery to come up so that I can get the modified stock that you suggested?
Thanks for your help, regardless
Androboss1994 said:
Okay, I will flash what you suggested but that's the problem. I am unable to access TWRP recovery from my Kindle. When it boots up there is no yellow flame that appears as the custom ROM is ICS 4.0.
I tried mounting a twrp.img on to the SD Card after downloading one straight onto the tab but of no avail :/
What do you suggest? Is there any way I can get the TWRP Recovery to come up so that I can get the modified stock that you suggested?
Thanks for your help, regardless
Click to expand...
Click to collapse
I know you said you read "close to a 100 articles" in your OP, but I suggest you do a little more reading. Get yourself acquainted with the key software components of the Kindle Fire and how they work together. Some of the things you say in your posts suggest you would benefit from the first post here...
http://forum.xda-developers.com/showthread.php?t=1552547
- The yellow flame you are looking for is an older version of the FireFireFire (FFF) bootloader, but there is a newer/better version.
- The KF cannot go to "the moving colorful discs straight on" because the first thing you will see is the bootloader's bootlogo.
- You must determine what bootloader is currently installed on the device because it is key in determining how you can get into recovery (TWRP).
- "Mounting" sdcard means to make the storage space available to either the host computer or the Kindle Fire, but it almost always means the former. Your comment about having "tried mounting a twrp.img on to the SD Card" doesn't make sense.
My guess is you do not have FFF installed and the device is booting with the stock bootloader. Odds are you will still be able to boot into your current ICS system and execute an adb command to set the bootmode to recovery (5001). Then a reboot should take you into TWRP. At that point, you should try to mount the sdcard partition onto your computer and transfer the latest FFF and whatever ROM you want to flash. Be sure to install FFF as soon as possible. This will allow you to get back into TWRP even if your system software becomes unbootable. Only when you are comfortable with FFF and TWRP should you consider flashing another ROM onto the device.
In broad strokes, the above paragraph contains the steps you will take to get your device running properly again. If any part of it doesn't make much sense to you, I suggest you read the above article again. Then, you can figure out the specifics commands from the third post of the link above and the following...
http://forum.xda-developers.com/showthread.php?t=1638452
kinfauns said:
I know you said you read "close to a 100 articles" in your OP, but I suggest you do a little more reading. Get yourself acquainted with the key software components of the Kindle Fire and how they work together. Some of the things you say in your posts suggest you would benefit from the first post here...
http://forum.xda-developers.com/showthread.php?t=1552547
- The yellow flame you are looking for is an older version of the FireFireFire (FFF) bootloader, but there is a newer/better version.
- The KF cannot go to "the moving colorful discs straight on" because the first thing you will see is the bootloader's bootlogo.
- You must determine what bootloader is currently installed on the device because it is key in determining how you can get into recovery (TWRP).
- "Mounting" sdcard means to make the storage space available to either the host computer or the Kindle Fire, but it almost always means the former. Your comment about having "tried mounting a twrp.img on to the SD Card" doesn't make sense.
My guess is you do not have FFF installed and the device is booting with the stock bootloader. Odds are you will still be able to boot into your current ICS system and execute an adb command to set the bootmode to recovery (5001). Then a reboot should take you into TWRP. At that point, you should try to mount the sdcard partition onto your computer and transfer the latest FFF and whatever ROM you want to flash. Be sure to install FFF as soon as possible. This will allow you to get back into TWRP even if your system software becomes unbootable. Only when you are comfortable with FFF and TWRP should you consider flashing another ROM onto the device.
In broad strokes, the above paragraph contains the steps you will take to get your device running properly again. If any part of it doesn't make much sense to you, I suggest you read the above article again. Then, you can figure out the specifics commands from the third post of the link above and the following...
http://forum.xda-developers.com/showthread.php?t=1638452
Click to expand...
Click to collapse
WOW! Okay, thank you so much; I'll keep you updated. I'll do all this tonight! Cheers :good:
okay so heres what happened.
I have an international htc one x that is indeed rooted with no roms installed.
I did create a back up and then tried to install the MIUI rom (but I dont really know where that is on my phone. I know I made one with rom manager. I dont have any backups on my computer though)
It worked, however, it didnt have wifi or data signals so i went back to try again.
I opened my bootloader screen. For the record, it is unlocked and hboot is version 1.73 if that helps.
I wiped cashe/data/delvic everything and even factory reset and installed the MIUI RD rom now hoping it would have a difference.
The darn thing got stuck on the MIUI bootloader for hours.
I did the same thing again a few times, sometimes in different orders and then it passed on and another screen came saying 'starting apps'. That got stuck for hours too.
Now I don't have any other roms on my phone, just the MIUI RD. The original miui just vanished too, i dont see it anymore. Also, when I put my USB wire to the phone and connect it to the pc, I cant transfer newer files into it. So this is all I have access to on my phone apparently.
I tried flashing a boot.img and a couple kernels but no luck. I've been trying to do this for all day and this is my first time so I don't know much about it.
I've been googling and somethings say to open cmd and type but i keep getting 'fastboot is not recognized as an internal or external command'
Currently, its not stuck at either the MIUI screen or the Starting Apps. but just the HTC logo screen and not going past.
I don't really want to install any new roms considering i've worked really hard to get this to work and I really want it now more so.
How do i fix this? I want to use this rom.
flash philz recovery (http://forum.xda-developers.com/showthread.php?t=2240646), usb mounting should work on that, then:
steps to install ROM
1. bootloader version should be 1.3x
2. copy ROM to SD Card
3. copy boot.img INCLUDED in the ROM zip to fastboot folder
4. flash the boot.img in fastboot
5. in recovery, wipe system/data/cache/everything
6. flash rom
7. restart
but how exactly do i put it on my phone? my computer isnt detecting my phone when i connect it? im sorry im not exactly an expert on this.
Go to recovery - mounts and storage - hook up the usb cable - tap the last option in the mounts and storage list and wait a few minutes. It won't be mounted instantly
ok i flashed the philtz recovery but when i flash the boot.img it says:
Finding update package
Opening update package
Installing update
installation aborted
for reference: http://forum.xda-developers.com/showthread.php?t=1957490
thats the rom i used and i flashed the boot.img flasher thats right above the download link
edit: also i tried just flashing the rom again and im still stuck on the HTC screen.
its not even going to the miui screen or starting apps anymore. :[
Boot.img must be flashed via fastboot. Not via recovery !
ok, i looked up how to fastboot, downloaded sdk files and i moved the boot.img into the fastboot folder and i opened command prompt there and wrote fastboot flash boot boot.img but i keep getting:
'fastboot is not recognized as an internal or external command'
what did i miss?
EDIT: ok, so the fastboot folder i got from the page didnt work so i used a different fastboot folder, dragged the .boot there and now it worked! finally passed the screen and wifi is connecting!
thank you!
Good, thanks to @tomascus. He summed it up real nice
Cheers
I made a very noob mistake today. I was going to factory reset my Oneplus 3 in TWRP (recovery) and flash back to the stock rom but I accidentally checked off everything to be erased... which erased my current operating system, along with the stock rom I was going to install :crying:
Now im stuck with no OS, phone won't boot, can only get into recovery etc etc
I tried connecting it to the computer and clicking MOUNT in recovery, my PC detects it, but when I try to drag and drop the stock rom it just hangs there and the file transfer progress bar doesnt move.
What are my options ?
The phone is rooted
You can use sideload from twrp. Or you can put the zip you want to flash in a usb and flash it via otg.
613BulletProof said:
I made a very noob mistake today. I was going to factory reset my Oneplus 3 in TWRP (recovery) and flash back to the stock rom but I accidentally checked off everything to be erased... which erased my current operating system, along with the stock rom I was going to install :crying:
Now im stuck with no OS, phone won't boot, can only get into recovery etc etc
I tried connecting it to the computer and clicking MOUNT in recovery, my PC detects it, but when I try to drag and drop the stock rom it just hangs there and the file transfer progress bar doesnt move.
What are my options ?
The phone is rooted
Click to expand...
Click to collapse
Put the OOS you want to install on a flash memory and use it as OTG from TWRP
As mentioned above, sideload is the easiest way.
Simply follow the steps here:
https://twrp.me/faq/ADBSideload.html
You can transfer data from a pc in twrp so you have loads of options
Push it with ADB
Ex- "adb push (input_file_name) /sdcard/(output_file_name)"
I will try adb sideloading, i had tried that method a while back for installing a rom and had issues, i have windows 10.
Skinpipe said:
You can transfer data from a pc in twrp so you have loads of options
Click to expand...
Click to collapse
already tried that it wont let me. it detects the phone on my pc, but when dragging and dropping it wont transfer and throws an error saying device could not be found.
613BulletProof said:
already tried that it wont let me. it detects the phone on my pc, but when dragging and dropping it wont transfer and throws an error saying device could not be found.
Click to expand...
Click to collapse
Try reflashing twrp from fastboot
I had the same problem when I was trying to upgrade to OOS 4.0. The phone was stuck at bootscreen. I powered it off by holding power button for 10 seconds. I turned it on again and booted in recovery mode. Then I connected my OP3 to PC and I was able to copy the .zip file into the TWRP folder. In recovery mode I installed the latest firmware from the .zip file.
Maybe I should mention that the OS I'm using is Arch Linux. My PC instantly recognized my phone.
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.