Rooting Order of Operations - Kindle Fire Q&A, Help & Troubleshooting

Can someone please tell me if this is the correct order to root a kindle. I am trying to avoid bricking. Have read though so many posts here, i'm all confused as what is right and what is not.
Does this make sense ?
1. Install Permanent Root with Superuser
2. Install the TWRP custom recover
3. Install the FireFireFire Bootloader
4. In TWRP, Wipe, Cache and then Daivk Cache, then Factory Rest
5 In TWRP, Install rom, then Wipe, Cache and then Daivk Cache and reboot.
Any suggestions appreciated.

http://forum.xda-developers.com/showthread.php?t=1552547
http://forum.xda-developers.com/showthread.php?t=1638452

Related

[Q] N00b updating Custom ROM

I have installed MildWild CM-2.7 on my Desire but there is now MildWild CM-2.8 and I can't find a guide how to install/update my Desire.
I have got S-OFF and recovery by Revolutionary The guide I followed to S-OFF and ROOT
This is the ROM I using. MildWild CM ROM
Just flash it via recovery like you did with the previous version
Will flashing the new version cause me to loose everything on my current version I.e apps and data etc??
Thanks for the reply though
do back up first, wipe davik+cache and flash it... it should work if not do full wipe and restore back up
just post any result we will move from there
What should I use to hackup TIbackup? Or is there a better one that you reccomend?
Wh000sher
Titanium and recovery. All basic stuff. Have a,read of my rooting faq in my signature. Tells you everything you need to know
Sent from my HTC Desire using Tapatalk
rootSU said:
Titanium and recovery. All basic stuff. Have a,read of my rooting faq in my signature. Tells you everything you need to know
Sent from my HTC Desire using Tapatalk
Click to expand...
Click to collapse
Do I only restore the Titanium I am guessing, as restoring recovery would revert back to my current ROM? and I have thanks
Yes indeed. With titanium, only restore "missing apps with data".
Theres a guide Angusc wrote here:
http://forum.xda-developers.com/showthread.php?t=1480343
ROM Manager can make updating so much easier - well worth the investment.
JohnHarrisNZ said:
ROM Manager can make updating so much easier - well worth the investment.
Click to expand...
Click to collapse
I can't speak for other devices but for Desire, nope it's not worth the time and money.
kotag82 said:
do back up first, wipe davik+cache and flash it.
Click to expand...
Click to collapse
So I'm only wiping the davik cahce correct?
Not anything else or have I missed something?
Wh000sher said:
So I'm only wiping the davik cahce correct?
Not anything else or have I missed something?
Click to expand...
Click to collapse
Things I've learned with all this flashing that may be helpful for you.
1. Before flashing, always backup your current system up. nandbackup via recovery, titanium for your apps, sd card if really needed for that you need to do.
2. If flashing an updated version of same rom, wipe cache and dalvik only on your recovery (unless explicitly specified by dev to make a full wipe.)
3. If you are having weird issues after upgrading the same rom, do a full wipe and start fresh. If issue is not resolved, report the issue to the Dev's thread.
4. Do a Full Wipe on recovery (System/factory, cache, dalvik if coming from a different rom).
stankyou said:
Things I've learned with all this flashing that may be helpful for you.
1. Before flashing, always backup your current system up. nandbackup via recovery, titanium for your apps, sd card if really needed for that you need to do.
2. If flashing an updated version of same rom, wipe cache and dalvik only on your recovery (unless explicitly specified by dev to make a full wipe.)
3. If you are having weird issues after upgrading the same rom, do a full wipe and start fresh. If issue is not resolved, report the issue to the Dev's thread.
4. Do a Full Wipe on recovery (System/factory, cache, dalvik if coming from a different rom).
Click to expand...
Click to collapse
Thanks for the reply.
In response to 2. I am using ClockworkMod as my Recovery and I am guessing you mean I have to wipe 'cache partition' and 'wike dalvik cache' under advanced?
I am creating a guide to help fellow N00bs how to update a rom and change between ROM's
Wh000sher
Wh000sher said:
Thanks for the reply.
In response to 2. I am using ClockworkMod as my Recovery and I am guessing you mean I have to wipe 'cache partition' and 'wike dalvik cache' under advanced?
I am creating a guide to help fellow N00bs how to update a rom and change between ROM's
Wh000sher
Click to expand...
Click to collapse
Yes if I remember correctly there are the first three lines on that recovery is wipe system, cache partition (like you stated), and wipe dalvik. So if upgrading just wipe cache partition and dalvik cache.
System partition is where the "Android OS" resides. Wiping it is like formatting your computer. Most of the time, incremental updates of the same rom requires you to wipe just the cache partition and dalvik, otherwise if the rom update has a lot of changes, the dev might require you to wipe all three options on the recovery.
Having wiped my cache and dalvik cache. I am now wanting to install the new version. On the main screen I have 2 options which are tempting to click.
One is 'Apply update from SD card' and the other is 'Install zip from SD card'
I am unsure of which to choose but my gut instinct is to go with 'Install zip from SD card', is this correct or am i going to make a terrible mistake?
wh000sher
Install zip from SD

HELP! T-989 Cant Flash Another Rom

Hey I am new to this so I had a T-989 running on 4.1.2 or something and so I installed CWM and rooted it using the T-989 toolkit. Afterwards I forgot to wipe and installed CM10. I was stuck on the booting screen for 40 mins and when I tried to go back to CWM it didnt work. So using the same toolkit I flashed the stock ROM. The stock seems to be gingerbread 2.3.6 and now the toolkit will not recognize it. Please help. I want it to run on CM10
Forget the toolkit and do it manually. First do you still have root? Try installing twrp recovery , you will have much less problems. Or try cwm again and make sure you follow the steps provided. Usually it's wipe/format, then format system, flash rom, wipe dalvick, wipe cache partition, fix permissions, reboot.
badaphooko01 said:
Forget the toolkit and do it manually. First do you still have root? Try installing twrp recovery , you will have much less problems. Or try cwm again and make sure you follow the steps provided. Usually it's wipe/format, then format system, flash rom, wipe dalvick, wipe cache partition, fix permissions, reboot.
Click to expand...
Click to collapse
Thanks for the info I was able to flash a 2.3.6 Gingerbread ROM onto my S2 using the toolkit and then from there on I had to reinstall the CWM and root and then using another guide I used the DarkSide wipe and reinstalled everything manually. Solved. Thank you.

[Q] Need help, i can only access twrp recovery mode

I was advised that i needed to update my recovery to twrp from cwm recovery to avoid an issue i got while flashing roms (the contents of my sd card would get pushed down into a subfolder of a newly created set of folders) however when i wiped my phone, as i always used to do with CWM twrp seems to have wiped a lot more, its wiped the existing rom, and all the files on my card, so i cant install a new rom. Basically i only have access to twrp recovery mode, how can i get the rom .zips onto my phone to install them? Id really appreciate any help at all, i had no issues flashing with CWM and i really dont know what to do.
download a rom/gapps and use adb to transfer them to your sdcard.. adb command "adb push file.zip /sdcard/file.zip"..
PS- in twrp wiping data wipes EVERYTHING so when you want to wipe before flashing a rom do a factory reset and DONT wipe data
Khizar said:
download a rom/gapps and use adb to transfer them to your sdcard.. adb command "adb push file.zip /sdcard/file.zip"..
PS- in twrp wiping data wipes EVERYTHING so when you want to wipe before flashing a rom do a factory reset and DONT wipe data
Click to expand...
Click to collapse
Thanks for your help, i found a similar problem on another site im halfway through it now, so when i flash roms in twrp i want to do a factory reset? wipe the cache and dalvik cache?
quirkles said:
Thanks for your help, i found a similar problem on another site im halfway through it now, so when i flash roms in twrp i want to do a factory reset? wipe the cache and dalvik cache?
Click to expand...
Click to collapse
this is how i flash roms..
1. factory reset
2. wipe system
3. wipe cahce
4. wipe dalvik
5. flash rom
6. flash gapps
7. flash AK kernel
8. reboot
9. wait 10 mins then do another reboot then enjoy :good:
quirkles said:
I was advised that i needed to update my recovery to twrp from cwm recovery to avoid an issue i got while flashing roms (the contents of my sd card would get pushed down into a subfolder of a newly created set of folders) however when i wiped my phone, as i always used to do with CWM twrp seems to have wiped a lot more, its wiped the existing rom, and all the files on my card, so i cant install a new rom. Basically i only have access to twrp recovery mode, how can i get the rom .zips onto my phone to install them? Id really appreciate any help at all, i had no issues flashing with CWM and i really dont know what to do.
Click to expand...
Click to collapse
You actually only had to update CWM to the latest version to fix that problem
EddyOS said:
You actually only had to update CWM to the latest version to fix that problem
Click to expand...
Click to collapse
eh, what's done is done, if it gives me any trouble ill switch back

Reset without rooting

Hello, i want to reset my n7100 without a custom kernel or rooting, with just a .zip recovery that disappears after a reboot. I want to wipe data, cache, dalvik, and fix permissions.
I tried to install in recovery mode recovery and recovery touch but i recieve an error with something like signature. Can you give me a recovery that works please? Thank you in advance.

Phone won't boot to OS after installing magisk. My experience

So i rooted my phone sometimes ago, and it worked fine at first but after some reboots it is now stuck at Redmi logo and would boot to fastboot mode after a while. Now i want to share my experience so people can be more careful, i may be a newbie but i do want to help people too.
So here's what my phone is using, CorvusOS 7.0 and SiLonT kernel and no more modifications other than that. Now i have read stuff online that some people have experienced bootloops and some can't boot to the OS they rooted their device with magisk. I have also read that dirty flash may solve the problem. But if you're already facing this problem maybe you can try these methods below:
Method 1: probably the easiest one, wipe the Dalvik and the cache
1. Reboot to your custom recovery
2. Go to advanced wipe (location and UI may differs between custom recoveries)
3. Simply tick Dalvik and cache and untick anything else
4. Reboot
Method 2: uninstalling magisk (this will unroot your device)
1. Download magisk uninstaller.zip (if you didn't downloaded it already from the start. Also make sure the uninstaller is the same version as your magisk version, idk what will happen if you do it with a different version but just in case )
2. Reboot to your custom recovery
3. And simply just flash/install the magisk uninstaller.zip, this will delete all magisk's files
4. Wipe Dalvik and cache (just in case)
5. Reboot
Method 3: dirty flash (for custom ROMs)
1. Uninstall magisk (follow method 2)
2. Get/download your custom ROM you are using (make sure it's the same ROM and version as the ROM you're using rn)
3. Flash it without wiping anything
4. Wipe Dalvik and cache (just in case, again)
5. Reboot
Method 4: reinstall/install your ROM, for custom ROMs users (I'm sorry i am not experienced with XiaomiFlashTool so i can't tell you how to flash stock ROM)
1. Backup all data cause this will erase all your data
2. Reboot to recovery
3. Uninstall magisk (follow method 2)
4. Wipe system, data, cache, Dalvik (the usual stuff you would wipe before installing a custom a ROM)
5. Install your chosen ROM
6. Wipe Dalvik and cache (just in case)
7. Reboot
If those methods above doesn't work you can try searching a tutorial on flashing the stock ROM on the internet, but if you still didn't manage to get your phone boot to the OS again then i am sorry to say that you have to take your phone to the nearest repair center.
So, what's the cause of this problem?
Well, it's simple, every human make mistakes, At least once. So it is normal to make mistakes. The developers are humans too so it is normal for them to make mistakes too, so instead blaming them we should support them and give them advice. But on the other side you may did a mistake too, probably a similar mistake that i did. Like maybe you did something wrong according to the tutorial, or you flashed an incompatible version of magisk, and etc. So from now on always ask if it's compatible, whether it's about magisk versions, ROM compatibility, kernel compatibility, recovery compatibility, and etc. And always double check just in case.
If i did something wrong tell me down below and I'll fix it as soon as possible.
Peace.
One quick little note: i fixed my device by doing a dirty flash (method 3) just to let you know
Edit: Phone won't boot after uninstalling magisk*, that was supposed to be title. Sorry I just realized sometimes ago
This happens to me all the time when flashing Android 11 ROMS. Curiously this doesn't happen when flashing Android 10 ROMs. I also never had this issue with TWRP, only OrangeFox.
But it could be other things too. For example, Xiaomi.eu 12.5 always go into a bootloop here, and trying to go back to any other ROM after flashing it leads to a boot loop. The fix is to flash disabled vbmeta if you're flashing xiaomi.eu 12.5. That might be the fix for A11 roms too but I never tried.
More than once it happened to me too that no matter what I did the phone would be stuck in bootloops with any ROM, any recovery. In that case, flashing stock rom via fastboot fixed the issue.

Categories

Resources