Related
Apologies for this stupid question resulting from a stupid mistake. Hoping somebody will be able to walk me through getting out of this.
I successfully rooted my sprint hero, then loaded modaco 3.0 (yes now I know that was bad). On reboot, the phone hangs on the black htc screen, and will respond to nothing.
The only thing I've been able to do is remove the battery, then turn it on in recovery mode. There, I did a wipe data/restore factory setting. Then I rebooted - and got the same boot screen, same problem.
Second try: wiped, toggled to usb, and replaced the 3.0 update.zip with the 1.1 for CDMA, tried to flash it, got this:
can't open /sdcard/update.zip (bad)
When I try to restore, I get these:
(bart) error: run bart via adb
(nandroid) can't open file
Please help! I am out of ideas. Thanks very much in advance.
you'll probably have to take it back to the very beginning......
Get the Sprint RUU stock rom (a couple of posts below this one) and run that
then re-root your hero
Flash one of the roms ON THIS BOARD ONLY!!! Any other Hero rom is meant for the GSM version so it will give you the same headache again.
thanks
Thanks for the quick response! I'll try that.
Hmm, not looking good here. When I tried to install the stock hero RUU I got this error:
no signature
verification failed
which I presume is related to the htc sync requirement for that rom in the unrooting procedure that I did earlier.
Any idea for working around that?
So you used RUU_Hero_C_Sprint_1.29.651.1_signed_release.exe? If not, here is a link to it: link.
david.danaan said:
Second try: wiped, toggled to usb, and replaced the 3.0 update.zip with the 1.1 for CDMA, tried to flash it, got this:
can't open /sdcard/update.zip (bad)
Click to expand...
Click to collapse
Don't use 1.1, grab a later one.
Which recovery? 1.5.x won't let you go back to the main menu without disabling USB-MS again... I don't remember what 1.2.3 did. If worse comes to worst, reboot the phone after copying the file.
gu1dry said:
So you used RUU_Hero_C_Sprint_1.29.651.1_signed_release.exe? If not, here is a link to it: link.
Click to expand...
Click to collapse
Yes, that's the one.
Using recovery 1.5.1. I can try a later rom, see if that works. I think I downloaded 1.3.
So first off yes, you aren't booting past the HTC screen because you flashed the wrong rom. However you aren't bricked. It's almost impossible to do once you're rooted and have RA's recovery installed unless you flash radios and stuff which you shouldn't.
Explanations for your other problems:
1. RUU doesn't work on the phones that are coming from the factory with 1.56. http://geekfor.me/news/sprint-ruu-fails/
There is a possible work-around but it's pretty detailed and I haven't gotten it to work. But you don't need to RUU if you can get in to RA.
2) (nandroid) can't open file is likely caused by RA 1.5.1. It had a bug that corrupted the backups. 1.5.2 is out. But for now don't worry about that cause your backup already sounds corrupted, nothing you can do.
3) can't open /sdcard/update.zip (bad). To me that sounds like your update was just corrupted.
How to fix it:
1. Boot in to recovery. With phone powered off hold your home button and then power.
2. Download fresh rom from http://geekfor.me/new-release/fresh-rom-1-0/ (what can I say... I'm partial. )
3. Within RA enable USB toggle and copy fresh rom to the root of your sdcard. Don't worry about renaming it to update.zip
4. Disable usb toggle. Go to flash zip from SD and choose fresh. That should be it. If you get the error saying the zip is bad then compare your downloaded copy with the md5 hash check on the download page (google it if you aren't sure how). If it matches then it's possible you have a bad sdcard. If it doesn't match then your downloads are crappy.
working!
Got it working by flashing the modaco v1.3a - must have been a bad update.zip before like you said. Thank you so much for the help and clear explanations, I was really worried I had bricked it.
David, now that it is working, I would recommend updating your recovery to 1.5.2.
I just want to thank everyone that posted to this reply I honestly thought that I bricked my phone and thank to you guys I was able to revive it. Thank you again.
I had a lot of problems trying to root my phone after I upgraded my firmware to 2.2 using the SuperOneClick application however, I did manage to come up with a fix that worked for me.
(Please note: that I can not be held responsible for any damage this may cause to your phone)
When I first tried using the SuperOneClick I notice that the applicaiton would hang "waiting for device". I received the following advice but it didn't work:
When the application gets to the "Waiting for device" prompt complete the following.
-Unplug usb from phone
-Uncheck usb debugging
-Replug usb cable
-Unplug usb cable
-Recheck usb debugging
-Replug usb cable.
Rince and repeat until successful rooting.
If you have tried this and it didn't work then try the following:
Google JuneFabrics PdaNet Andriod and download / install the PdaNet for Android.
During the installation you will be prompted to install new USB drivers so that your phone can connect to your PC. However, if you have ever connected your phone to Kies or for file transfer then say no to the install.
Once you have the program installed go back to SuperOneClick and run as administrator.
Happy Rooting...
It worked for me on my second try without having to download PdaNet, but I know it can be a pain in the a$$
SuperOneClick worked for me on first try on Captivate 2.2!
Also worked first try on my friend's Bell Galaxy S.
z4 not workin on this?
SteveCheeseman said:
z4 not workin on this?
Click to expand...
Click to collapse
Haven't read any posting of it working.
I couldn't get z4root to work
Sent from my SAMSUNG-SGH-I896 using Tapatalk
No z4root is not working. The exploit it use only works on 2.1 not 2.2. The app will FC / freeze or just close.
Also just a note on the SOC. Please don't start thread saying the usb unplug/replug method worked or didn't for you. This IS the way it works. If it worked on your first try, well good for you go buy a lottery ticket cause it's your lucky day.
The success rate is 100% but the number of tries is random. Could work on your 5th attemp like it can on your 1st or 2th.
Sorry guys for my silly question
but what is super one click and where can i get it ?
Thanks
Or you could just download my new Rogers 2.2 ROM Fire Fly and not have to worry since it comes rooted
adamholden85 said:
Or you could just download my new Rogers 2.2 ROM Fire Fly and not have to worry since it comes rooted
Click to expand...
Click to collapse
Firefly's awesome - you're everywhere adam!
Clockworks Recovery
Hi,
I recently rooted my phone with Superoneclick, but I can't get the Clockword recovery working.
I got the following error message.
E:fialed to verify whole-file signature
E:signature verification failed
Could someone help me out on this?
Thanks,
I got error in sdcard\update.zip
(error 7) when trying to install on rogers captivate on eclaire 2.1
why??
tried 2 diff root files.
shaddowman said:
Sorry guys for my silly question
but what is super one click and where can i get it ?
Thanks
Click to expand...
Click to collapse
If you go to google and search Super One Click download, you should be able to find it that way.
help
Cokeaddict said:
Hi,
I recently rooted my phone with Superoneclick, but I can't get the Clockword recovery working.
I got the following error message.
E:fialed to verify whole-file signature
E:signature verification failed
Could someone help me out on this?
Thanks,
Click to expand...
Click to collapse
i have the same thing happening to me. tried superoneclick several times, it works, i flash clockworkrecovery works, then i reboot and get the same message. -brent
Cokeaddict said:
Hi,
I recently rooted my phone with Superoneclick, but I can't get the Clockword recovery working.
I got the following error message.
E:fialed to verify whole-file signature
E:signature verification failed
Could someone help me out on this?
Thanks,
Click to expand...
Click to collapse
Normal 3e clockwork recovery has signature verification which prevents a lot of the files here from being flashed on your phone (because they are not officially verified/signed). There's a modified 3e clockwork file that you can put on your phone. When I first installed it for my own rooted phone, I used untermensch's 3e_recovery_installer.zip which was easy and didn't require any terminal stuff.
hook up your phone to a computer with the galaxy s drivers (using PDAnet works great). then run the script. the script is kinda wonky so it took a few tries to work.
let us know how that goes
adamholden85 said:
Or you could just download my new Rogers 2.2 ROM Fire Fly and not have to worry since it comes rooted
Click to expand...
Click to collapse
I found that to actually flash this ROM, you need to do the steps I mentioned, above.
with 2.2 jp3 or jp2 , u don't need do root it so far . use Odin3 downgrade it to 2.1 and use oneclickroot .......... ( use adb to enter download mode with some model can't use 3 button . "fastboot reboot download"
this superoneclick does not work
I have tried this method multiple times, all seems to go right, i get superuser showing up in my app drawer, yet when i use clockworks recovery to flash a new recovery I get the "failed to verify whole-file signature" followed by the next line "signature verification failed Installation aborted"...
I have the rogers captivate, it has been updated to android 2.2, Android system recovery <3e>.
I have also tried the adb version of rooting with the same result. Not sure if anyone has actually gotten theirs to work on rogers, they really should make a video or a more detailed list. Im not new to rooting or anything, but the instructions versus the results are not adding up. Hope there are others with success stories that they would like to share.
WOW you know you have 3e recovery. Search info on it.
you will find that 3e has signature verification... thats why your zips fail!!!
you will also find the 3e recovery FIX..
IT WAS FULLY EXPLAINED 2 POSTS ABOVE YOURS this friggin page!!! up 10 inches!!!
WHAT THE F????
http://forum.xda-developers.com/showthread.php?t=909213
Fail
I have tried the untermensch's 3e_recovery_installer.zip method, but ended up bricking my phone. Thankfully rogers sent me a new one when i complained that it was the devices fault. Has this worked on anyones captivate.
yeah the version you flashed was for a vibrant not a captivate...
use the instructions Posted above and in my sig "3e fix"
why is this the most difficult thing this month when its an old problem?
Today I installed my first rom, it was called dl09_supah_clean_04. That worked ok but I could not receive text messages. I thought maybe I'd try another rom. So I downloaded one called hamsters rom. Once I booted the phone up with that rom I got a bunch of errors. So I restarted and now get nothing but the samsung logo flashing. I go into recovery mode, click on update.zip to load clockwork recovery and get a message saying:
e:can't mount /dev/block/vold/179:9
(no such file or directory)
e:can't mount sdcard:update.zip
Installation aborted
I'm just wondering if I am screwed here. I'm about to plug the sdcard into my computer and copy update.zip again in hopes of getting clockwork recovery to work.... just wondering if anyone has any ideas in case this doesn't work.
You need to put it on the phones internal sd card plus sometimes you need to put text message setting yourself like message centres number .
Sent from my GT-I9000 using XDA App
Is this a troll?
mdisaac said:
Today I installed my first rom, it was called dl09_supah_clean_04. That worked ok but I could not receive text messages.
Click to expand...
Click to collapse
That's because you have to install a DL09 kernel and modem as well.
I thought maybe I'd try another rom. So I downloaded one called hamsters rom.
Click to expand...
Click to collapse
How clueless are you?
That's a i9000 ROM. Or Captivate port.
Every single flashing thread warns
DO NOT FLASH ANYTHING NOT SPECIFICALLY FOR THE VERIZON FASCINATE
You flashed a GSM ROM onto a CDMA phone. That's just asking for a brick.
Now download this (and since you can't figure obvious things out, flash it into *PDA* of Odin, NOT NOT NOT NOT NOT "phone"), and pray it works.
THANK YOU, THANK YOU, THANK YOU!!
My phone is back and working on the stock rom. I am definitely clueless when it comes to this but I am not giving up. I am going to get the dl09_supah_clean_04 rom working. I'll be more careful this time though.
Thanks again!
s44 said:
Is this a troll?
That's because you have to install a DL09 kernel and modem as well.
How clueless are you?
That's a i9000 ROM. Or Captivate port.
Every single flashing thread warns
DO NOT FLASH ANYTHING NOT SPECIFICALLY FOR THE VERIZON FASCINATE
You flashed a GSM ROM onto a CDMA phone. That's just asking for a brick.
Now download this (and since you can't figure obvious things out, flash it into *PDA* of Odin, NOT NOT NOT NOT NOT "phone"), and pray it works.
Click to expand...
Click to collapse
not trying to be a d!ck but, you really need to stop before you do brick your phone. read, read, and read some more. its clear you dont understand what your doing and are going to end up screwing up even worse. read EVERYTHING dealing with ONLY the VZN fascinate. if it says anything other that VZN fascinate DO NOT READ IT. your in to big of a hurry and will brick your phone. hell, i have been hacking phones for years and am still not comfortable with android yet. i have rooted but not installed a rom because i dont want to mess it up. hell, i havent even done the new update from VZN. im waiting for more reports to come in. just take your time and read, then worry about flashing to another rom.
If you mess your phone up just use odin and the official stock DL09.md5 to return the phone to normal. Easy.
mdisaac said:
Today I installed my first rom, it was called dl09_supah_clean_04. That worked ok but I could not receive text messages. I thought maybe I'd try another rom. So I downloaded one called hamsters rom. Once I booted the phone up with that rom I got a bunch of errors. So I restarted and now get nothing but the samsung logo flashing. I go into recovery mode, click on update.zip to load clockwork recovery and get a message saying:
e:can't mount /dev/block/vold/179:9
(no such file or directory)
e:can't mount sdcard:update.zip
Installation aborted
I'm just wondering if I am screwed here. I'm about to plug the sdcard into my computer and copy update.zip again in hopes of getting clockwork recovery to work.... just wondering if anyone has any ideas in case this doesn't work.
Click to expand...
Click to collapse
You also need to odin the DL09 modem. or SMS and other things WILL be broken.
1.4hitachi said:
If you mess your phone up just use odin and the official stock DL09.md5 to return the phone to normal. Easy.
Click to expand...
Click to collapse
When people take Odin for granted, they end up with bricks.
Odin can be your friend...as long as you use PDA and not Phone...which is counter intuitive
adrynalyne said:
When people take Odin for granted, they end up with bricks.
Click to expand...
Click to collapse
Shouldn't you say, 'when people use Odin incorrectly"? I mean, as long as he follows the instructions and un-does and kernel changes beforehand the device will be returned back to stock. Also with the official DL09.md5 package it has inside all necessary operating parts. It sounds to me like all he did was attempt a rom flash twice. Odin with the "offical" DL09.md5 will return his Fascinate to stock.
Thanks everybody! I got back to stock and let phone receive the ota update of DL09. Figured that would take care of the kernel and modem and I could install dl09_supah_clean_04. Worked like a champ. I think I learned a lot in this process as well... time will tell.
GT P1000xwjp9
So i got my Carphone Warehouse unlocked tab, I've read and re-read a million post until my eyes hurt.
The Tab had already been updated to the latest Gingerbread release via Kies.
First step was to root the phone, now z4root and superonclick won't work because the tab was up to date.
So, i ran Odin and followed this thread.
[11.05.2011][CF-Root v3.3] JJ*, JM*, KA*, JQ1 - su+busybox+CWM3/RFS - xda-developers
All worked perfectly, rooted tab running stock rom.
BUT, i didn't want to stay with the stock rom, i wanted this Modoco ROM.
04/Feb Fr1 - MoDaCo Custom ROM for the Samsung Galaxy Tab with Online Kitchen - Android @ MoDaCo
I followed instructions to the letter. and it appeared to work fine.
But it didn't the tab is now constantly rebooting and I'm stuck.
On further investigation it appears the method i used to root the tab installs a "CUSTOM" CMW, and i think this is incompatible with the Modoco rom. There is a problem in that Modoco Rom needs ext/4? and the custom CMW doesn't allow for that.
So to me (laymans terms) i need to either somehow get a stock rom installed or get proper CWM on phone and reflash it.
Also to make matters worse, as soon as i try to put in ANY text the tab instantly restarts (so market is out for now) also when plugged into pc tab still constantly restarts (so Odin is out)
But the phone will boot into some form of CWM and will run an update zip fine. (from external sd card only)
So i need some help getting this tab up and running so i can actually have some fun with it.
When i try and reflash from internal card the tab doesn't "see" that card, and if i connect to the pc the only option i get is to mount the card, but even then the tab restarts after a few seconds.
Nandroid restore won't work because of these messages:
"sd-ext.img not found. Skipping restore of /sd-ext
I've tried to do a factory reset, but when it's finished it comes up with an error
E:failed to mount /sd-ext (Invalid argument)
Error mounting /sd-ext!
Also Clockwork recovery app has now gone missing, (it appears to be replaced by a small green circle, when i click on it, it does give me the option to reboot into recovery) i can't re-install it from the market, because when i try to get to the market and type the bloody thing reboots itself.
riverboat2001 said:
GT P1000xwjp9
So i got my Carphone Warehouse unlocked tab, I've read and re-read a million post until my eyes hurt.
The Tab had already been updated to the latest Gingerbread release via Kies.
First step was to root the phone, now z4root and superonclick won't work because the tab was up to date.
So, i ran Odin and followed this thread.
[11.05.2011][CF-Root v3.3] JJ*, JM*, KA*, JQ1 - su+busybox+CWM3/RFS - xda-developers
All worked perfectly, rooted tab running stock rom.
BUT, i didn't want to stay with the stock rom, i wanted this Modoco ROM.
04/Feb Fr1 - MoDaCo Custom ROM for the Samsung Galaxy Tab with Online Kitchen - Android @ MoDaCo
I followed instructions to the letter. and it appeared to work fine.
But it didn't the tab is now constantly rebooting and I'm stuck.
On further investigation it appears the method i used to root the tab installs a "CUSTOM" CMW, and i think this is incompatible with the Modoco rom. There is a problem in that Modoco Rom needs ext/4? and the custom CMW doesn't allow for that.
So to me (laymans terms) i need to either somehow get a stock rom installed or get proper CWM on phone and reflash it.
Also to make matters worse, as soon as i try to put in ANY text the tab instantly restarts (so market is out for now) also when plugged into pc tab still constantly restarts (so Odin is out)
But the phone will boot into some form of CWM and will run an update zip fine. (from external sd card only)
So i need some help getting this tab up and running so i can actually have some fun with it.
When i try and reflash from internal card the tab doesn't "see" that card, and if i connect to the pc the only option i get is to mount the card, but even then the tab restarts after a few seconds.
Nandroid restore won't work because of these messages:
"sd-ext.img not found. Skipping restore of /sd-ext
I've tried to do a factory reset, but when it's finished it comes up with an error
E:failed to mount /sd-ext (Invalid argument)
Error mounting /sd-ext!
Also Clockwork recovery app has now gone missing, (it appears to be replaced by a small green circle, when i click on it, it does give me the option to reboot into recovery) i can't re-install it from the market, because when i try to get to the market and type the bloody thing reboots itself.
Click to expand...
Click to collapse
Hi,
If you can get into CWM, you can flash the new Hyperdroid 1.4.8 for the Tab. Check the thread to get the correct instructions to do so. Mind you, there's also a Hyperdroid kernel made by AF974. It's included in the ROM, it should fix all your issues, if not I advice to flash the kernel after the ROM one more time...
Thanks so much for the reply.
I have a few questions before i go any further.
I used this :http://forum.xda-developers.com/showthread.php?t=885734
to root phone. If i follow your suggestions will i still be rooted?
I really want to use the Modoco rom that I've baked, will i be able to do that?
(I like having the choice of what to install)
Is Hyperdroid 1.4.8 a ROM or a different custom recovery?
How do i actually flash this Hyperdroid 1.4.8?
is it using an update zip?
What do i do with these three files:
(26-1-12) HDRP_V1.0.1-BETA-CWM Flashable
HDRP_V1.0.0 CWM Flashable
HDRP_V1.0.0 TAR Odin flashable
There are also THREE attached zip files to that thread - which one would i need?
Also If i could find the correct xwjp9 gingerbread rom i assume i could use that to at least get the tab up and working.
BYW... what in laymans terms is a Kernel?
I've never had these problems on my phones, always
1/root
2CWM
3/nandroid
4/install rom after rom =no problems!
PS. i tried just reflashing (via odin) this file http://forum.xda-developers.com/showthread.php?t=885734&page=35
And now tab doesn't even get past the Samsung screen, so it's actually in a worse state than it was this morning.
Wish i'd never started this....Bugger
E:unknown volume for path [E/sytem:]
E:unable process volume1 skipping
checking /data
E:unknown volume for path [/data]
E:unknown volume for path [/data]
E:unable to process volume! Skipping...
checking /cache
E:unknown volume for path [/cache]
E:unknown volume for path [/cache]
E:unable to process volume! Skipping...
E:unknown volume for path [/cache/recovery/command]
E:can't mount /cache/recovery/command
E:unknown volume for path [/cache/recovery/log]
E:can't mount /cache/recovery/log
Ecan't open /cache/recovery/log
E:unknown volume for path [/cache recovery/last_log
Ecan't mount /cache/recovery/last_log
Ecan't open/cache /recovery/last_log
E:unkown volume for path [/cache/recovery/command
riverboat2001 said:
Thanks so much for the reply.
I have a few questions before i go any further.
I used this :http://forum.xda-developers.com/showthread.php?t=885734
to root phone. If i follow your suggestions will i still be rooted?
I really want to use the Modoco rom that I've baked, will i be able to do that?
(I like having the choice of what to install)
Is Hyperdroid 1.4.8 a ROM or a different custom recovery?
How do i actually flash this Hyperdroid 1.4.8?
is it using an update zip?
What do i do with these three files:
(26-1-12) HDRP_V1.0.1-BETA-CWM Flashable
HDRP_V1.0.0 CWM Flashable
HDRP_V1.0.0 TAR Odin flashable
There are also THREE attached zip files to that thread - which one would i need?
Also If i could find the correct xwjp9 gingerbread rom i assume i could use that to at least get the tab up and working.
BYW... what in laymans terms is a Kernel?
I've never had these problems on my phones, always
1/root
2CWM
3/nandroid
4/install rom after rom =no problems!
PS. i tried just reflashing (via odin) this file http://forum.xda-developers.com/showthread.php?t=885734&page=35
And now tab doesn't even get past the Samsung screen, so it's actually in a worse state than it was this morning.
Wish i'd never started this....Bugger
E:unknown volume for path [E/sytem:]
E:unable process volume1 skipping
checking /data
E:unknown volume for path [/data]
E:unknown volume for path [/data]
E:unable to process volume! Skipping...
checking /cache
E:unknown volume for path [/cache]
E:unknown volume for path [/cache]
E:unable to process volume! Skipping...
E:unknown volume for path [/cache/recovery/command]
E:can't mount /cache/recovery/command
E:unknown volume for path [/cache/recovery/log]
E:can't mount /cache/recovery/log
Ecan't open /cache/recovery/log
E:unknown volume for path [/cache recovery/last_log
Ecan't mount /cache/recovery/last_log
Ecan't open/cache /recovery/last_log
E:unkown volume for path [/cache/recovery/command
Click to expand...
Click to collapse
OK, first off I am no expert on this and I may have to be corrected.
Can you get the tab into download mode? (long press power + volume down)
If so, does Odin recognise the connection? (yellow box on the comX where x is an arbitrary number - always 6 for me)
If you answer yes to the two above I would suggest getting re-stocked. You can do this with comprehensive instructions found at the Team Overcome Guide
...next you *could* install the Overcome Kernel (instructions + link in the guide above) which will convert you to Ext4.
I am not 100% sure if you are rooted at this point but you can always check after reboot and root as necessary.
Now (after checking for root and acting accordingly) you should be in a position to install you Modoco ROM (I think )
riverboat2001 said:
Thanks so much for the reply.
I have a few questions before i go any further.
I used this :http://forum.xda-developers.com/showthread.php?t=885734
to root phone. If i follow your suggestions will i still be rooted?
I really want to use the Modoco rom that I've baked, will i be able to do that?
(I like having the choice of what to install)
Is Hyperdroid 1.4.8 a ROM or a different custom recovery?
How do i actually flash this Hyperdroid 1.4.8?
is it using an update zip?
What do i do with these three files:
HDRP_V1.0.0 CWM Flashable
HDRP_V1.0.0 TAR Odin flashable
There are also THREE attached zip files to that thread - which one would i need?
Also If i could find the correct xwjp9 gingerbread rom i assume i could use that to at least get the tab up and working.
BYW... what in laymans terms is a Kernel?
I've never had these problems on my phones, always
1/root
2CWM
3/nandroid
4/install rom after rom =no problems!
PS. i tried just reflashing (via odin) this file http://forum.xda-developers.com/showthread.php?t=885734&page=35
]
Click to expand...
Click to collapse
Hi,
Hyperdroid 1.4.8 is indeed a full ROM with kernel included. The HDRP is the sole kernel, which can be flashed via CWM in existing compatible ROMs (= 2.3.6 )
CWM-flashable means you can flash the file via CWM - install zip from SD... and the Hyperdroid is rooted as in 'standard issue'
The CF-rom you flashed played the same trick to me also LOL, try reflashing it again. However , if you can get into CWM, I'd suggest you flash first the HDRP v1.0.0.zip, then let it reboot and set the filesystem to ext4, then get back into the 'new' CWM and flash the Hyperdroid 1.4.8zip.
Or , if you prefer to install your Modaco-brew, better take a look in the Overcome-guide to restock and start over again with the Modaco-ROM.
phlooke said:
OK, first off I am no expert on this and I may have to be corrected.
Can you get the tab into download mode? (long press power + volume down)
If so, does Odin recognise the connection? (yellow box on the comX where x is an arbitrary number - always 6 for me)
If you answer yes to the two above I would suggest getting re-stocked. You can do this with comprehensive instructions found at the
...next you *could* install the Overcome Kernel (instructions + link in the guide above) which will convert you to Ext4.
I am not 100% sure if you are rooted at this point but you can always check after reboot and root as necessary.
Now (after checking for root and acting accordingly) you should be in a position to install you Modoco ROM (I think )
Click to expand...
Click to collapse
Hi,
I can get into recovery, and download mode, and Odin does see tab.
So I'm currently downloading the GB Safe Rom.
(only got 1mb connection - taking forever!)
Can i ask what method you used to root your tab?
Many Many Thanks for your help.
I had figured out about 50% of what was needed, but would have taken so much longer with your help.
Edit: Update. Got the stock Gingerbread ROM up and running, now onto the next part of the list, but all going well so far.
Hope this post might help someone else stuck on this, Cheers.
PS, have "lost" root and really want it back for the nandroid and titanium pro!
Edit:
Bloody Modoco ROM
Got my tab all up and running using the fantastic guide at Overdrive that you pointed me to.
Now i followed that guide right through to the end and had the overdrive rom installed.
I performed a Nandroid backup instantly.
At this point, i must have lost my mind as i decided to have another go at the modoco rom.
Same result, constant reboots and instant reboots on text entry, so something definatley wrong there.
Then i tried to use the Nandroid that i had made. but it wouldn't work, again complaining that it couldn't see the drive.
So' I've started all over again.
PS Still not got root, and can't see how to get it if z4root and super-one-click don't work.
riverboat2001 said:
Hi,
I can get into recovery, and download mode, and Odin does see tab.
So I'm currently downloading the GB Safe Rom.
(only got 1mb connection - taking forever!)
Can i ask what method you used to root your tab?
Click to expand...
Click to collapse
The Overcome ROM is already rooted.
riverboat2001 said:
Many Many Thanks for your help.
I had figured out about 50% of what was needed, but would have taken so much longer with your help.
Edit: Update. Got the stock Gingerbread ROM up and running, now onto the next part of the list, but all going well so far.
Hope this post might help someone else stuck on this, Cheers.
PS, have "lost" root and really want it back for the nandroid and titanium pro!
Edit:
Bloody Modoco ROM
Got my tab all up and running using the fantastic guide at Overdrive that you pointed me to.
Now i followed that guide right through to the end and had the overdrive rom installed.
I performed a Nandroid backup instantly.
At this point, i must have lost my mind as i decided to have another go at the modoco rom.
Same result, constant reboots and instant reboots on text entry, so something definatley wrong there.
Then i tried to use the Nandroid that i had made. but it wouldn't work, again complaining that it couldn't see the drive.
So' I've started all over again.
PS Still not got root, and can't see how to get it if z4root and super-one-click don't work.
Click to expand...
Click to collapse
LOL..
What is it about Modoco that you want?
You should try Overcome for a time. It's rooted - so you'll be fine with TB etc. - stable and fast.
phlooke said:
The Overcome ROM is already rooted.
LOL..
What is it about Modoco that you want?
You should try Overcome for a time. It's rooted - so you'll be fine with TB etc. - stable and fast.
Click to expand...
Click to collapse
LOL ... in my country we have a saying : (translated) a donkey never trips twice on a stone.. To prove you're not a donkey you have to trip twice LOLLLLL
dirlan2001 said:
LOL ... in my country we have a saying : (translated) a donkey never trips twice on a stone.. To prove you're not a donkey you have to trip twice LOLLLLL
Click to expand...
Click to collapse
Hehe...I like that
Hi,
As they suggested to you, the Hyperdroid Androidmeda v 1.4.8 is ery good for you, as you can go through recovery mode via CWM, you can download zip files and flash them through CWM in recovery mode, the rom is making full wipe and it is rooted
These problems may have been caused by Ext4, or rather the fact that standard Samsungs ROM's don't used Ext4, but the other ROM's do. You can't take Hyperdroid and flash it to a stock ROM. If you want to use Hyperdroid (I use it myself), you have to put Overcome on it first, because Overcome converts the file system to Ext4. So putting Overcome stock on the Tab should fix the boot problems, and after that you should be able to flash for instance Hyperdroid from CWM.
Thanks Guys
Rooted the tab, got overcome rom running beautifully on it.
Thanks so much for all your help........
You're gonna love this:
I think it's that great that I've gone and bought the Tab 7 Plus.
Hubby thinks I've gone bloody mad
Ps, the original reason for wanting the Modoco rom was that it was stripped bare of all the bloat and crap. I also am a paid subscriber so get access to bake my own roms.
Pretty good when you've got so many Android tabs/phones in one household.
Have to admit the Overcome ROM is a cracking rom
ableeker said:
These problems may have been caused by Ext4, or rather the fact that standard Samsungs ROM's don't used Ext4, but the other ROM's do. You can't take Hyperdroid and flash it to a stock ROM. If you want to use Hyperdroid (I use it myself), you have to put Overcome on it first, because Overcome converts the file system to Ext4. So putting Overcome stock on the Tab should fix the boot problems, and after that you should be able to flash for instance Hyperdroid from CWM.
Click to expand...
Click to collapse
Not quit true... You first flash the Hyperdroid RedPill kernel on whatever GB system. It will convert your system to ext4. Then you can flash wether the Hyperdroid ROM or the Overcome ROM.
So, I can't remember what I did to this device, exactly. I got it already in a bootloop. I had seemingly fixed it for a few weeks, but then it started rebooting randomly and then eventually got into another bootloop. I can't remember if that just happened one day or if I was trying to fix the random reboots.
I stopped working on it when a family member gave me their old Nexus 5X. But the other day my Nexus 5X entered into a bootloop because of its well known hardware problem (I think anyway, I wasn't doing anything that should have bricked it). So I decided to pull out the old Galaxy s5 and see if I can fix that instead.
Normally when I flash ROMs onto devices, I do it when the process for the device is pretty well established. As we all know, Samsung devices aren't the easiest to work with. So I remember having to do a bunch of extra ****, download Odin and so forth.
By the way, I have the AT&T G900A version. I boot into recovery and see that it boots into CWM, thats good news obviously. I pick "update through adb". I run ADB through command prompt (btw, someone should update the guides on this site to mention that Powershell doesn't play nice with ADB commands, that was like 20 minutes of hair pulling frustration) and it recognizes the device. I wipe all the user data and cache etc and attempt to flash a custom ROM I found on this site: APTOS found here.
I get an
Finding update package. . .
Opening update package. . .
Verifying update package. . .
E:footer is wrong
E:signature verification failed
So then I downloaded the stock firmware ROM titled "SM-G900A 4.4.2 G900AUCU1ANCE Firmware.rar" and get the same errors.
So, obviously I am forgetting something. I know there are a lot of guides on here and the answer is probably out there somewhere, the problem is that most of those guides are for people starting at square 1 without CWM or TWRP installed. Can anyone help me from where I am at? I uninstalled Odin a while ago but could definitely reinstall it. Was hoping to do this from where I am at, since CWM is already installed.
Anyone have any ideas on what step I'm forgetting? Do I need to flash other things before the ROM? Should I just start completely over with ODIN and the rest of it?
P.S. I have more experience with TWRP than CWM but I remember having trouble getting TWRP to work but did manage to get CWM to install as an alternative.
Thanks in advance!