Database Users

Help installing ICS!

I'm a relatively new user of the android device and I was wondering if someone could help me install ICS on my phone.
The first thing I did was the section 5 of this thread to root my phone: http://forum.xda-developers.com/showthread.php?t=1238070
Then, I tried following the instructions on this thread to install ICS: http://rootzwiki.com/topic/11850-romicsiml74k-teamhacksungs-ics-port-for-fascinate-build-5-0114/
One thing I noticed from reading around though, was that I needed to do a NANDROID backup. In order to do that, I downloaded the 'ROM Manager' and tried to 'Reboot into Recovery'. However, it wouldn't boot into recovery, so I did a quick search and figured out the solution, which was found here: http://www.addictivetips.com/mobile/how-to-install-clockworkmod-recovery-on-samsung-galaxy-s-i9000/
In order to solver this problem, I realized that I had to download a kernel that's applicable to my drive. I'm now looking at my kernel version to figure out which file to download, but I'm having a hard time going from there.
As you can see, I'm kind of all over the place, so I decided to stop before I screw up my phone. Can anyone please help me out or point me to the right direction?
Thank you!

Bauss said:
I'm a relatively new user of the android device and I was wondering if someone could help me install ICS on my phone.
The first thing I did was the section 5 of this thread to root my phone: http://forum.xda-developers.com/showthread.php?t=1238070
Then, I tried following the instructions on this thread to install ICS: http://rootzwiki.com/topic/11850-romicsiml74k-teamhacksungs-ics-port-for-fascinate-build-5-0114/
One thing I noticed from reading around though, was that I needed to do a NANDROID backup. In order to do that, I downloaded the 'ROM Manager' and tried to 'Reboot into Recovery'. However, it wouldn't boot into recovery, so I did a quick search and figured out the solution, which was found here: http://www.addictivetips.com/mobile/how-to-install-clockworkmod-recovery-on-samsung-galaxy-s-i9000/
In order to solver this problem, I realized that I had to download a kernel that's applicable to my drive. I'm now looking at my kernel version to figure out which file to download, but I'm having a hard time going from there.
As you can see, I'm kind of all over the place, so I decided to stop before I screw up my phone. Can anyone please help me out or point me to the right direction?
Thank you!
Click to expand...
Click to collapse
Use droidstyle's guide for everything. It is step by step, no way to fail.
Sent from my SCH-I500 using XDA App

First you don't need to root your phone to flash a new rom. We almost need his in big bold letters in the guide, because this is a huge misconception.
I never do.nadroids, I back up what I want and reinstall.the programs I need. You can always Odin back to stock if.something goes wrong. The advantage to rooting is that you.can now use titanium backup to back up your programs. (I have the least problems if I install them from the market and then restore data only.)
Then flash CWM fixed for CM7. Three finger into recovery. If the phone boots it will reflash the stock recovery and you'll have to flash it again.
Install ICS.
??
Profit.

I see You found section 5 in my guide, but you missed the part right at the top that says "this is not needed if flashing a custom rom". Also, how did you miss section 3 that has the exact instructions for putting ICS on your phone?

droidstyle said:
I see You found section 5 in my guide, but you missed the part right at the top that says "this is not needed if flashing a custom rom". Also, how did you miss section 3 that has the exact instructions for putting ICS on your phone?
Click to expand...
Click to collapse
Damn it, you're right. I guess I'm an idiot.
Is it OK that I go straight to section 3 right now? Or must I un-root the device first?

No your fine to move ahead, a rooted phone wont hurt you.

FIXED - Hard Brick Atrix

I included this in another thread but thought it might help more if it had its own thread.
Problem:
SVF:105:1:2
Failed to boot 0x1000
SOLUTION:
Download: http://dl.dropbox.com/u/23255832/Atrix Unlock/AUTOMATIC_UNLOCK_V4.2.zip
Download the program
- Once unzipped in a folder open the file MAIN
- Do the repair first (option 3)
- It gives you instructions as you go
- Then I did option 1, follow instructions and chose 2.3.4
- Phone is alive again
- Then I did option 3 and followed instructions.
Thats it, easy.
What a waste of a day. Do the repair first, then reload and you're good to go.

I just noticed the link doesn't work. It was an automatic root/cwm dos program that had a menu if anyone knows what I am talking about. I just cleaned up my pc and can't seem to find it either. Will keep looking for it.

Found it!
http://forum.xda-developers.com/showthread.php?p=24472332#post24472332
Its labeled AUTOMATIC_UNLOCK_V4.2

jjj133 said:
I just noticed the link doesn't work. It was an automatic root/cwm dos program that had a menu if anyone knows what I am talking about. I just cleaned up my pc and can't seem to find it either. Will keep looking for it.
Click to expand...
Click to collapse
Here it is, from the link you posted on the other thread (found it through the list of your posts):
http://forum.xda-developers.com/showthread.php?t=1182871

A few problems:
This tool already has it's own thread. And it is already known that this tool fixes failed to boot errors (I mean, it is Option 3).
You should not post the thing in multiple threads.
This post does not belong in the dev section.
Edit:
Forgot to mention that I am glad you got your phone working again.

My Phone is showing following message:
SVF:105:1:2
Failed to boot 0x1000
NVFlash...
Nothing more, and it is actually shutting down after few moments automatically.
Any hope? I had this issue long time ago, and it is still there.

yeah same here 0x1000 and it reboots so can't i fix this? I try holding down the volume down and it restarts any help?

has anybody tried on bell atrix?
thks

This is softbrich. Hardbrick not fix.

Sorry guys, meant soft brick but I couldn't change the title after I wrote it. I just wanted to put it up because when I bricked mine it took me like 7 hours to find all of the info on how to do this. Maybe is better documented now (this happened months ago to me). Still, I wanted to post to help others. Hope it helps

[Q] problem: n7 3g 32 jwr66y wont boot recovery

so i had jwr66v rooted with superSU twrp cmw 6.035 or whast ever.
now i have updated to ******y and i tried to flash a ROM in in CWM but it did nothing. at all. i rebooted into recovery only to get a droid on his back with a red ! coming out his belly. um problem here. i opened super Su and it said i need to reroot because i have installed 4.3
how can i reroot if i can't access recovery.
tried using toolkit to reroot (un root to stock first) but it froze now having this problem: post #455
http://forum.xda-developers.com/showthread.php?p=45162727&posted=1#post45162727

anyone?

Just flash recovery from cmd/terminal using fastboot.
Sent from my Nexus 7 using xda app-developers app

never used it. details would be nice.

Want details? There are stickies and tutorials for a reason. Lemme guess, you used a toolkit to root it the first time?
Sent from my Galaxy Nexus

sure I'll follow one of your tutorials. most of the time written as if we know every detail about android development jargon. oh and most tuts have missing details that usually means moderate technical knowledge people have to make assumptions when following those instructions. another issue I'm funding with following "stickies" is because there are so many different ways to update and so many different versions of root tools made by many different clever developers. sometimes they don't all work together. most of the time i will follow some developers half thrown together set of instructions only to have to redo the instructions 3 of 4 times because of the reasons all mentioned above.
short response to your reply. i followed a simple tutorial put up by a developer and most likely used a tool kit. now i have issues. rather then spend countless hours hunting for else who has had the same problem and actually posted it, i decided to ask the question so someone like yourself that enjoys spending hours each night balls deep in code can give me a simple link or basic set of instructions so i can have some relief.

Adb and fastboot. Those are the only tools you need to use.
If I had been in your shoes, I would have done a bit of googling on the term 'fastboot recovery'
I don't know why some people make this so hard. This is a developer site, if you don't want to learn, you shouldn't be here. Considering all this **** is literally spelled out for you with step by step documentation, it doesn't make any sense to click that 'new thread' button when this issue is so common.
Sent from my Galaxy Nexus

yeah googling more is what got me following half arse instructions and wading hours of my day. so which part of your detailed instructions would have led you ( if in my shoes) to Google fast boot recovery?
well I have now downloaded the latest tool kit so i can un root. then I'm going to hunt through countless posts and try find which is the best way to root and install cm10.x hopefully next time their is an update i won't have to reroot just to get all my little root access apps back.
ps this is the trouble shoot q&a section not the developers only section. hence why i posted here.

Welcome to xda-DEVELOPERS.com.
Maybe you missed that part. The domain name isn't xda-hold-lazy-asses-hand-and-make-their-device-cool.com
You are expected to read, comprehend, and take initiative to learn. Asking for a hand holding session is not the way.
If you would bother reading the stickies, you would see how easy it is to flash recovery. There is a tutorial in the damn stickies that literally walks you through the process.
Hint: every goddamn nexus gets rooted and recovery flash the same way regardless of what version of android you are on
I don't know how much more plain and simple we could be here.
Fastboot flash recovery name of recovery.IMG
I mean wtf how could you NOT find that?
Sent from my Galaxy Nexus
since you are being so lazy, and i have obviously had enough to drink tonight:
http://forum.xda-developers.com/showthread.php?t=1907796
http://forum.xda-developers.com/showthread.php?t=2150661
http://wiki.cyanogenmod.org/w/Doc:_fastboot_intro
http://forum.xda-developers.com/showthread.php?t=2072732
http://forum.xda-developers.com/showthread.php?t=2175086
READ!
heres another hint. you need a recovery made SPECIFICALLY for your device 'tilapia'

so..... thanks for the pointless rant, after re read many guides and how tos, also wasting a saturday. still cant get the bootloader to update from version 4.13 (read post 1 again) not even using fastboot. Also read post #455 http://forum.xda-developers.com/showthread.php?p=45162727&posted=1#post45162727

aza510 said:
so..... thanks for the pointless rant, after re read many guides and how tos, also wasting a saturday. still cant get the bootloader to update from version 4.13 (read post 1 again) not even using fastboot. Also read post #455 http://forum.xda-developers.com/showthread.php?p=45162727&posted=1#post45162727
Click to expand...
Click to collapse
Use stock images for Android 4.2 and not 4.3 to avoid that error.
But i'm not sure why you want to flash anything else than recovery? Do you want to get it back to pure stock?

Unlocked Bootloader splash/boot page?

Presumably like all of you who have unlocked your bootloader, I am faced each time I boot with the garbage page with random text telling me "my software cannot be checked for corruption". Can anyone tell me where that page is stored (partition or folder) would be thankful for any information.

metpolds said:
Presumably like all of you who have unlocked your bootloader, I am faced each time I boot with the garbage page with random text telling me "my software cannot be checked for corruption". Can anyone tell me where that page is stored (partition or folder) would be thankful for any information.
Click to expand...
Click to collapse
Its not random, and if you look closer its a bootmenu. you can get past it marginally quicker by just tapping power button or use it to boot to recovery, fastboot/bootloader, etc.
And you cannot remove it.

You can go back to b20...

@nujackk and @lafester .. Thanks both of you for your comments. @nujackk I accept that the screen is a way of booting into fastboot mode, I just never used it, before I installed TWRP I always used MiFav Recovery to boot into fastboot. I am presuming that the screen is an integral part of the boot image and I shall continue to try and hunt it down.
@lafester as always lol your comment.
If either of you are interested I am just going to set up a new thread in "Themes Apps and Mods" where I shall post 3 flashable zip boot animations and hopefully in the coming days I will add to them.

metpolds said:
Presumably like all of you who have unlocked your bootloader, I am faced each time I boot with the garbage page with random text telling me "my software cannot be checked for corruption". Can anyone tell me where that page is stored (partition or folder) would be thankful for any information.
Click to expand...
Click to collapse
The screen is part of the bootloader image. I strongly advise you to just live with it since if you screw up the bootloader you're bricked.

Might I suggest you start by looking around in the bootloader unlock zip. Might give you some idea where it is or if it can be removed.
Also look at older list mentioning it, I remember seeing mention of other phones it's been used on, maybe someone has more info in one of those forums.
And I will look for those boot animations. If I can suggest a superman or superAndy would be nice
Good Hunting

metpolds said:
@nujackk and @lafester .. Thanks both of you for your comments. @nujackk I accept that the screen is a way of booting into fastboot mode, I just never used it, before I installed TWRP I always used MiFav Recovery to boot into fastboot. I am presuming that the screen is an integral part of the boot image and I shall continue to try and hunt it down.
@lafester as always lol your comment.
If either of you are interested I am just going to set up a new thread in "Themes Apps and Mods" where I shall post 3 flashable zip boot animations and hopefully in the coming days I will add to them.
Click to expand...
Click to collapse
I know what you are talking about - on older motorola phones we did away with it - it was just a stored image in those phones. Seeing as how here it is a fully functional menu I would bet any attempt to remove or replace it would most definitely brick the phone. I gave up on it a long time ago.

@lafester .. @nujackk .. @bkores .. @tabletalker7 .. Thanks guys for all your comments - I guess my next step eventually, there is no great hurry for this, is to make certain I have a couple of good backups before messing around with disassembling the bootloader and boot image. If I ever get anywhere with this I will let you guys know.
@nujackk I note your comments re the animations. I'm about to add another Andy animation to the thread but have searched in the past for usable Superman material without much success, however I will see what I can find.

Yeah I haven't seen many that were very good either, but keeping hope alive :fingers-crossed:

Oneplus 6T bricked in fastboot loop...Please help!

Hi there. I am a a bit of a root-moron and have bricked my brand new Oneplus 6T while rooting it. Now I am stuck in a bootloop that ONLY cycles through the fastboot.
I can no longer enter into recovery mode from fastboot.
I can not use the MSM Download tool because the phone will not go into MSM Mode. Whenever I connect to the USB the phone automatically “wakes up” and immediately goes into fastboot.
When I hold the power button + volume up it just cycles through all the fastboot options and when it does eventually power down / screen goes black, it immediately powers back up and does the exact same thing.
So I simply cant get into MSM mode or recovery mode. I don’t know what to do and fear that the phone may be totally f#cked.
I welcome assistance from anyone here who actually knows what they are doing vs me who knows close to nothing. Help please!

OP6TNewb said:
Hi there. I am a a bit of a root-moron and have bricked my brand new Oneplus 6T while rooting it. Now I am stuck in a bootloop that ONLY cycles through the fastboot.
I can no longer enter into recovery mode from fastboot.
I can not use the MSM Download tool because the phone will not go into MSM Mode. Whenever I connect to the USB the phone automatically “wakes up” and immediately goes into fastboot.
When I hold the power button + volume up it just cycles through all the fastboot options and when it does eventually power down / screen goes black, it immediately powers back up and does the exact same thing.
So I simply cant get into MSM mode or recovery mode. I don’t know what to do and fear that the phone may be totally f#cked.
I welcome assistance from anyone here who actually knows what they are doing vs me who knows close to nothing. Help please!
Click to expand...
Click to collapse
First question, what exactly did you try to flash so we can get you the correct help on what to do from here.

Problem SOLVED!!!
justibasa said:
First question, what exactly did you try to flash so we can get you the correct help on what to do from here.
Click to expand...
Click to collapse
Thanks for your follow up.
Just want to let you now that I fixed it using the Stock Fastboot tool posted here
https://forum.xda-developers.com/oneplus-6t/how-to/rom-stock-fastboot-roms-oneplus-6t-t3862516
I just did exactly as instructed; my phone was already stuck in fastboot so I plugged to my PC and ran the flash-all.bat file. I really didn't think it would work because the phone did not seem to respond or do anything. I went to the toilet, came back and it was reset to factory!!!! Amazing.
Thank you so much @mauronofrio for posting this amazing tool. You saved my bricked phone! I sent you a donation for your assistance. Thanks again.

Just for future reference, as long as you can get this phone into fastboot, you should be fine. For now that's where all the flashing happens until we get a custom recovery.
But I'm glad to hear you fixed it lol

Can I just point out how bad*** of a "newb" the OP is. Dude signs up to XDA, literally makes his account name "OP6TNewb" then proceeds to give zero f**** and immediately jumps into flashing his brand new phone (as we all did once!). THEN he fixes the issue on his own using a tool he found by SEARCHING and THEN HE DONATED TO THE DEV WHO CREATED THE TOOL!!!!!
Kudos to you @OP6TNewb. All "newbs" should aspire to be like you.

Pain-N-Panic said:
Can I just point out how bad*** of a "newb" the OP is. Dude signs up to XDA, literally makes his account name "OP6TNewb" then proceeds to give zero f**** and immediately jumps into flashing his brand new phone (as we all did once!). THEN he fixes the issue on his own using a tool he found by SEARCHING and THEN HE DONATED TO THE DEV WHO CREATED THE TOOL!!!!!
Kudos to you @OP6TNewb. All "newbs" should aspire to be like you.
Click to expand...
Click to collapse
Thank you for the kind words. Donating was an easy choice because the tool saved me $650. If a guy in my situation doesn't stand up and donate to rewards you guys then who will???
Thanks again to @mauronofrio for the amazing tool and thank you to this community for allowing newbs like me to somewhat safely explore the world of android rooting & modifications.

OP6TNewb said:
Thank you for the kind words. Donating was an easy choice because the tool saved me $650. If a guy in my situation doesn't stand up and donate to rewards you guys then who will???
Thanks again to @mauronofrio for the amazing tool and thank you to this community for allowing newbs like me to somewhat safely explore the world of android rooting & modifications.
Click to expand...
Click to collapse
Out of mere curiosity, what exactly did you do to cause the device to go into bootloop anyhow?

Pain-N-Panic said:
Out of mere curiosity, what exactly did you do to cause the device to go into bootloop anyhow?
Click to expand...
Click to collapse
They probably have gone off to brag to their friends about what happened. Lol
I, too, am curious about what he did. It's been so long since I first began tinkering, but certainly remember some times I goofed.
Sent from my ONEPLUS A6013 using Tapatalk

Pain-N-Panic said:
Out of mere curiosity, what exactly did you do to cause the device to go into bootloop anyhow?
Click to expand...
Click to collapse
Hi Pain & Panic.
I was attempting to root my device following the instructions here https://www.xda-developers.com/oneplus-6t-unlock-bootloader-root/ by Adam Conway.
I was successful up to flashing the twrp img file but I made the error of flashing the wrong zip file. (blu_spark_r54-oos-pie_op6-6t_12869fe.zip ). This is bc when you follow the link to the twrp download page in Adam's instructions, the actual twrp zip file you need as per the instructions is the 10th file down the list and I didn't realize that this was important vs using the 1st zip file on the page which is the one I used. I assumed that the other files were older versions and the 1st was the most recent update that I should use. For a newb like me, this was VERY confusing.
Once I flashed the zip and rebooted to system, I got stuck in the fastboot bootloop.
While I am not 100% sure that this is what caused the problem, and maybe you will tell me that the zip file shouldn't have made a difference, but these are the steps I took.
FYI - after restoring my device using @mauronofrio's tool, I have successfully rooted my phone by following Adam Conway's steps and using the EXACT files he screenshots on the tutorial. So after a painful but educational experience, I rooted my device. Thanks again!

OP6TNewb said:
Hi Pain & Panic.
I was attempting to root my device following the instructions here https://www.xda-developers.com/oneplus-6t-unlock-bootloader-root/ by Adam Conway.
I was successful up to flashing the twrp img file but I made the error of flashing the wrong zip file. (blu_spark_r54-oos-pie_op6-6t_12869fe.zip ). This is bc when you follow the link to the twrp download page in Adam's instructions, the actual twrp zip file you need as per the instructions is the 10th file down the list and I didn't realize that this was important vs using the 1st zip file on the page which is the one I used. I assumed that the other files were older versions and the 1st was the most recent update that I should use. For a newb like me, this was VERY confusing.
Once I flashed the zip and rebooted to system, I got stuck in the fastboot bootloop.
While I am not 100% sure that this is what caused the problem, and maybe you will tell me that the zip file shouldn't have made a difference, but these are the steps I took.
FYI - after restoring my device using @mauronofrio's tool, I have successfully rooted my phone by following Adam Conway's steps and using the EXACT files he screenshots on the tutorial. So after a painful but educational experience, I rooted my device. Thanks again!
Click to expand...
Click to collapse
I forgot to mention one thing which may also be the reason. Initially, before using Adam Conways instructions, I started with the steps on High on Android (Max Lee) for the OP6 but on their download page, I mistakenly downloaded the twrp zip for the 5T and I flashed it. This initially cause the device to brick but I got it back into fastboot and into recovery and thats when I flashed the OTHER twrp file above. After I did this, I could no longer get into recover and was stuck in fastboot only.
So you can see that I made multiple errrors and I am not sure which one lead to what. Thank goodness OnePlus is friendly to rooting so I could save the phone!

OP6TNewb said:
Hi Pain & Panic.
I was attempting to root my device following the instructions here https://www.xda-developers.com/oneplus-6t-unlock-bootloader-root/ by Adam Conway.
I was successful up to flashing the twrp img file but I made the error of flashing the wrong zip file. (blu_spark_r54-oos-pie_op6-6t_12869fe.zip ). This is bc when you follow the link to the twrp download page in Adam's instructions, the actual twrp zip file you need as per the instructions is the 10th file down the list and I didn't realize that this was important vs using the 1st zip file on the page which is the one I used. I assumed that the other files were older versions and the 1st was the most recent update that I should use. For a newb like me, this was VERY confusing.
Once I flashed the zip and rebooted to system, I got stuck in the fastboot bootloop.
While I am not 100% sure that this is what caused the problem, and maybe you will tell me that the zip file shouldn't have made a difference, but these are the steps I took.
FYI - after restoring my device using @mauronofrio's tool, I have successfully rooted my phone by following Adam Conway's steps and using the EXACT files he screenshots on the tutorial. So after a painful but educational experience, I rooted my device. Thanks again!
Click to expand...
Click to collapse
Ah, I see. Looks like you flashed a kernel zip instead.

Im not a noob, but have been so out of practice with the latest Android ROMS and flashing and the changes in the partition arrangements. I managed to soft brick my phone as well and this post totally saved the day! Mauronofrio totally deserves a donation and I also gave one.
Thanks XDA! This place has saved me many times and helped me get the most of all my Android devices!

Hey guys. i am also no noob in flashing/rooting my devices.
Don thishundres of times.
Today my OP6T has shown an Magisk update (before it was 21.4 + Magisk Manager) and now it showed the popup to update -> done and error "bad image format" (i think for the kernel). Rebooted and now i am stuck in the same fastboot bootloop.
Tried to boot up TWRP with "fastboot boot tmrp.img" sadly it doesnt boot.
Any hints how i can recover my phone without wiping everything?
maybe @mauronofrio has an idea?
thx a lot

Other users facing the same issue with magisk 22, see here: https://forum.xda-developers.com/t/...oot-roms-for-oneplus-6t.3862516/post-84553217