Database Develop

Problems after rooting / flashing my phone

Hey everyone,
Sorry to be creating a new topic on this but I have literally spent the last 3 hours trying to figure this out and have searched the entire forum looking for answers and couldn't find any.
Here's the deal. I was following this guide on rooting my phone and got all the way to the image part. I was going to install this build which mentioned I needed the DangerSPL. Went ahead and followed this guide on how to install the DangerSPL and got to the flashing DangerSPL part, where I was supposed to install the CM 5.0. (Note: When trying to install the CM 5.0 I also get the e: can't find update script as well)
There's where the problem happened. After getting that in my phone will not go any further than the T-Mobile G1 screen. It just freezes there and there it stay. I tried updating the CM 5 but it always gives me the message e:can't find update script, and that's downloading straight from the website and then renaming it to update.
So as of right now I don't know where to go, I'm pretty stuck at this point. I don't know if I should be doing something to prevent the can't find the update script message or what, or how to get past the G1 screen.
Any help will be deeply appreciated as I'm stuck without a phone at the moment.
Thanks a lot in advance.
Edit:
Update: By returning to "factory" settings I was able to at least start up the phone, so that's a positive. Negative is that it is now a 1.0 version of the droid, so I would much rather be able to install something slightly better but I still have been running into the error can't find update script on several different builds.

Ouch.... I feel your pain... 1.0 is pretty old. Few questions before troubleshooting:
1. What phone do you have: G1, Dream, Roger's Dream.. etc
2. What does it say in your H/F boot (power up using camera and power button and copy 4 lines that you will see)
3. What build are you on right now (Menu-Setting-About phone)
Once we have that - we can proceed.

Edit:
After going through the steps again as I restored factory settings the rooting and upgrading finally did work. Go figure.
Thanks for the help, it was really appreciated.

[Q] Issue loading recovery

Hi guys,
Followed the steps in forum.xda-developers.com/showthread.php?t=736271 to root my N1. All worked ok, and had root access. I proceeded to flash a custom recovery and received an error "mtd: not writing bad block at 0x000xxxxx". I redownloaded the recovery again, with the same issue. I rebooted and found that the recovery had loaded, however, after another reboot, was no longer the Amon recovery, but stock?
Second question is how can i unroot and go back to full stock? Tried a method found in another threat but was receiving a "verification failed" error - i assume because the version being flashed was too old for the FRF91 i had.
Any help is appreciated

Update
Hi ended up downloading EPE76 and renaming it to passimg, and letting recovery find/run it to unroot.
I then upgraded to FRF85B by downloading and renaming it to update.zip and running it from recovery.
And finally, i downloaded FRF91 and renamed to update.zip and ran it, again from recovery console, to get back to where i was before the hassles.
Not sure if this was the correct way to unroot, but my radio, rom version etc all matches before i started the rooting. The recovery flash never stuck (even though i did it in manual mode), and so it seems i am stock again.
Any advice on the issues in my first post?

best way to root
http://forum.xda-developers.com/showthread.php?t=710842

had same issue while rooting my latest nexus one, not exactly sure of how it happend but I just did same process and it worked fine. Command error or adb push into wrong place. I just cut and paste commands and it worked out fine.
First nexus one I unlocked bootloader and ended up selling it, thinking of switching to iphone 4, but decided to stay with n1.

Update
Hi there...
The method i used is a copy of that but without the battery mod.
Didn't really think having to trim the battery pack was a great idea...

Update
osugsxr said:
had same issue while rooting my latest nexus one, not exactly sure of how it happend but I just did same process and it worked fine. Command error or adb push into wrong place. I just cut and paste commands and it worked out fine.
First nexus one I unlocked bootloader and ended up selling it, thinking of switching to iphone 4, but decided to stay with n1.
Click to expand...
Click to collapse
Yeah starting to wonder if i should even bother trying again... just not sure if CM will be worth the effort. Was more doing it to check it out, rather than a need.
If i can find out how to unroot properly (i may have done it correctly above), i may give it another go. Just felt my unroot effort was trial and error and not really game to try it again and stuff it completely.

HELP! Galaxy Tab Frozen

While trying to update my Galaxy Tab's Overcome mod using the instruction on the site, I failed to read the part that said "Do note that you should NEVER update Overcome ROMs across different bases, like 1.4.x to 1.6.x or God Forbid, 1.4.x/1.6.x to 2.x! You need to do the full-shebang listed below…". When I tried to boot up the Tab, the standard T-mobile screen came up, followed by the picture attached. Does anybody have a possible fix for this?

*sighs* thats why we say read the guide fully before attempting to flash. Do that first. After you're done read it again. It will tell you everything. Start by booting into download mode and restocking to the stock firmware then follow guide directions word by word to install FULL overcome.
PS make sure your tab is well charged and your FINAL warning: REAd THE GUIDE!

Thanks...but how do you restore to stock firmware? I can't seem to find a guide that makes sense to me (I'm new to this). I don't really want to attempt to follow the guide and mess up again...

Medikay said:
Thanks...but how do you restore to stock firmware? I can't seem to find a guide that makes sense to me (I'm new to this). I don't really want to attempt to follow the guide and mess up again...
Click to expand...
Click to collapse
this is the stock firmware from t-mo, thanks to rotohammer.
http://forum.xda-developers.com/showthread.php?t=855851

Sorry for all the questions, but, after restoring to stock and following the install instructions for Overcome v2.0.0, my Tab has been stuck at the "the Overcome experience" screen for quite some time now. When going through the instructions, there was only one step I did not follow exactly; on step 6, instead of letting the Tab automatically reboot (it never did), I manually rebooted it. After that, I put the zip folder on an external sd card (the Tab would not boot and instead stayed on the "android" screen) and installed overcome...Should I restore again?

Slight problem

Followed all the instructions re bootlocker and rooting......... I have not however got cwm on the phone. Is it ok to jump in on the last part of the tool kit and try again. Obviously I need this last bit to be able to instal roms etc. I guess I cant just down load cwm and instal ?
Advise and directions most appreciated.
sr

Bootloader fails in Odin, not sure what went wrong

Hello I'm not really that good with mobile tech so excuse my noobness but i decided to dive in and try to root my samsung s6. Here is step by step what i've done so far
Following a few tuts after backups i rooted my phone and verified it with root checker.
Next I downloaded a few popular root apps and removed a bunch of bloatware on the phone
Today I decided to try to install a custom ROM for my phone, after finding a suitable one for my model I proceeded with his guide:
http://forum.xda-developers.com/gal...xtrestolite-deodexed-mod-edition-1-0-t3094423
Next I downloaded all the correct files (I'm confident I double checked)
Now I'm not sure if this is where I went wrong but I installed TWRP custom recovery first
Then I proceeded to install modem with Odin and that went fine it passed and phone restarted
But when I go to install bootloader under BL in Odin it just fails, tried 3 times same result
Can anyone suggest another step in troubleshooting this? If it helps I was running stock samsung os never tinkered with the phone before this
Any advice is appreciated and please let me know if there is any more info i can provide
Thanks
EDIT:
Ok so I posted this late last night after trying to figure it out for a while. This morning I left for work to discover I had no mobile capabilities at all. No data, call, text nothing. Last night I was connected to my wifi at home so I guess I didn't notice. This has been obviously brutal with no communication all day. I tried tinkering a bit with it (did a factory reset through TWRP, tried flashing everything through TWRP) and nothing really helped.
Now I'm not really sure how to proceed so any advice would help as I don't want to brick my phone. What I'm planning on doing next that is the only thing that makes sense to me (again I have very little experience with phones) is to:
1. Re-flash everything through TWRP
2. Re-flash using stock rom, stock bl, and stock modem using Odin
My questions are is there any particular order I need to do this in and also will I have to re-root the phone again after or will this just be the stock rom but still rooted?
Thanks again literally ANY ideas u can throw out here go a long way as I've opened myself a can of worms