I had been using ARHD 7.0 well. However, I found it laggy this morning. I tended to reflash the ROM.
I did it as usual. The AROMA INSTALLER said installation was successful.
When I hit the "reboot system now", the Samsung Galaxy Note 10.1 logo comes out and the get back into recovery.
I have tried replacing CWM 6.0.1.1 to TWRP 2.5 and checked the box of "wipe data partition" in AROMA. Yet they didn't help.
Anyone can suggest a solution for me!!:crying:
Have you tried installing a different rom? Or just odin back to stock?
I used odin to flash a stock rom and succeeded.
However I lost my root
I'll try flashing other roms once I get the root.
Related
I flashed stock 4.2.2 firmware through ODIN twice now. To make sure there was nothing wrong before. Right after flashing stock firmware, I installed PhilZ Touch 6.25.0 Recovery. In recovery, I tried installing several KitKat ROMs without incident (+gapps). But it never boots. The screen either powers off or boots to recovery. I've also tried using Dhollman KK kernel in case it was a kernel issue but that didn't work either. Not sure what's wrong.
I've tried both Philz 6.25.0 and CWM 6.0.4.7. Never any install errors, just doesn't boot. Stock firmware boots fine though.
EDIT: Even flashing stock firmware 4.2.2 (P5113UEUCMK3) through ODIN gets to bootloop at Samsung Logo now.
EDIT 2: So I can install recovery through ODIN, but installing ROMs does nothing. (Doesn't matter if it's 4.3 or 4.4. Stock frimware flashing through ODIN results in boot loop or boot to recovery as well.
pm2gonzales said:
I flashed stock 4.2.2 firmware through ODIN twice now. To make sure there was nothing wrong before. Right after flashing stock firmware, I installed PhilZ Touch 6.25.0 Recovery. In recovery, I tried installing several KitKat ROMs without incident (+gapps). But it never boots. The screen either powers off or boots to recovery. I've also tried using Dhollman KK kernel in case it was a kernel issue but that didn't work either. Not sure what's wrong.
I've tried both Philz 6.25.0 and CWM 6.0.4.7. Never any install errors, just doesn't boot. Stock firmware boots fine though.
EDIT: Even flashing stock firmware 4.2.2 (P5113UEUCMK3) through ODIN gets to bootloop at Samsung Logo now.
EDIT 2: So I can install recovery through ODIN, but installing ROMs does nothing. (Doesn't matter if it's 4.3 or 4.4. Stock frimware flashing through ODIN results in boot loop or boot to recovery as well.
Click to expand...
Click to collapse
if you are having a bootloop after flashing stock rom 4.2.2 then no problem cos after that to boot up you have to boot into recovery and wipe cache partition and do a factory reset and after than when you will boot into system after few minutes you will boot into screen without any problem
try a clean install wipe data and cahe, cache partition, davilik cache and format system.
Have a Verizon Samsung Galaxy Note II (SCH-i605). Took the latest OTA update to VRUEMJ9. Have since rooted and installed SafeStrap and was happily running N3BULA ROM, when I decided to explore a bit and tried to flash Alliance ROM. Now I'm stuck on the Samsung boot screen and can go no further. I am able to access Android system recovery, but when I try to 'apply update from external storage' I get 'E:signature verication failed' message. Tried to flash to stock via Odin, but unsuccessful. Shows Added in Odin but nothing happens when I select the .pit file or the .tar file. This is a work issued phone, so any help to get up and running would be greatly appreciated!
Brantosapien said:
Have a Verizon Samsung Galaxy Note II (SCH-i605). Took the latest OTA update to VRUEMJ9. Have since rooted and installed SafeStrap and was happily running N3BULA ROM, when I decided to explore a bit and tried to flash Alliance ROM. Now I'm stuck on the Samsung boot screen and can go no further. I am able to access Android system recovery, but when I try to 'apply update from external storage' I get 'E:signature verication failed' message. Tried to flash to stock via Odin, but unsuccessful. Shows Added in Odin but nothing happens when I select the .pit file or the .tar file. This is a work issued phone, so any help to get up and running would be greatly appreciated!
Click to expand...
Click to collapse
Have you performed a "wipe data" option from the recovery after flashing the alliance ROM (it wipes your user data)?
Because I just visited the alliance ROM thread ( http://forum.xda-developers.com/showthread.php?t=2032447 and in the install instructions its mentioned so.
Better take a little time and properly read the install instructions during flashing..
Sent from my GT-I9070 using Tapatalk
dagger said:
Have you performed a "wipe data" option from the recovery after flashing the alliance ROM (it wipes your user data)?
Because I just visited the alliance ROM thread ( http://forum.xda-developers.com/showthread.php?t=2032447 and in the install instructions its mentioned so.
Better take a little time and properly read the install instructions during flashing..
Sent from my GT-I9070 using Tapatalk
Click to expand...
Click to collapse
I never had that option. I've flashed numerous ROMS before and am pretty meticulous when it comes to following instructions. It appeared to have a custom flash script which allowed me to pick what I did and didn't want to install. I tried to keep it mostly stock and when it completed, it automatically rebooted (didn't give me an option to 'wipe data') and now leaves me stuck on the Samsung Boot Screen. I was able to flash the .pit file via Odin, but keep getting a 'MD5 hash value is invalid' when I try to flash the .tar file.
Brantosapien said:
I never had that option. I've flashed numerous ROMS before and am pretty meticulous when it comes to following instructions. It appeared to have a custom flash script which allowed me to pick what I did and didn't want to install. I tried to keep it mostly stock and when it completed, it automatically rebooted (didn't give me an option to 'wipe data') and now leaves me stuck on the Samsung Boot Screen. I was able to flash the .pit file via Odin, but keep getting a 'MD5 hash value is invalid' when I try to flash the .tar file.
Click to expand...
Click to collapse
You should enter into recovery and then manually wipe data..
Also if that thing doesnt work, then have a look at this thread which explains how to go back to stock rom..
In addition,
A. Why doesnt Odin work?
Did you unextract the tar and pit from the rar/zip so that odin could recognize the files as suggested in dagger's link in section 1b step 2?
Did you install samsung drivers on your computer properly? You may use this toolkit for that
B. Rescue by CWM
Signature verification failed is caused (I think) by stock samsung recovery's choosiness, if you are sure you downloaded the zip correctly. What zip did you exactly try to flash?
So now, you may want to flash a cwm recovery or a kernel that contains cwm inside. Flashing usually uses adb using fastboot. Search "flashing a recovery image" or "flashing a kernel" where your chosen kernel should have cwm inside. cwm usually does not put out that signature verification error.
Remember:
You can access recovery mode through an app or by pressing a button combo when turning your phone on. Device specific.
Stock samsung recovery can wipe data.
CWM can also wipe data, and is the preferred installation method for most/all custom roms. And it can make a nandroid backup.
If ever you do choose to flash, you'll need the toolkit to install adb/fastboot drivers, but maybe since yours in locked bootloader the adb thing might not work.
Hope this helps
Okay this is a weird one, Note 10.1 runs out of battery a few nights ago, go to plug it in for charging and it hangs on the "samsung galaxy note 10.1 screen". I had been running Cyanogen 11 for a few months just fine and before that Omni (Both 4.4.2) no dramas with CWM recovery 6.0.3.6. I can still get to Download/ODIN mode and CWM.
Now here is the fun part(s)
1. Firstly I tried reflashing the roms from CWM, after all I flashed both of them from the same recovery and they were still on the external sdcard. Both gave set metadata recursive status 7 error messages.
1.NB Whenever I selected the internal storage to search for a zip CWM would close immediately (crash?) and go back to the galaxy note 10.1 screen and hang there still. Also does this on other options, so I can't reach the backup I made on the internal storage
2. After googling that it seems that 6.0.3.6 can't flash 4.4.2 roms so I flash a later version using ODIN, it says success on the PC side, yet nothing changes in tablet, same when trying with twrp. CWM 6.0.3.6 won't budge
3. Try flashing the official rom (N8010XXUCMK2_N8010XSACNA2_HOME) from sammobile using ODIN, same problems as before, download mode shows the bar filling up so does ODIN, says it passed, still nothing.
4. Try old 10.2 Cyanogen build, no error message but still hangs on samsung galaxy note screen
5. Try repartitioning whilst flashing, various .pit also used, no dice. However I can now mount /data from cwm still can't mount /efs
6. Read about eMMC bug possibly being induced by Cyanogenmod, open up tablet to to check numbers on eMMC module, doesn't match any of the affected numbers.
7. Try above steps multiple times, including flashing each right after each other.
8. Cry
9. Look at new tablet options (Damn no good ones with softkeys)
10. Back to desperate flashing ODINing and scrolling through CWM
So any ideas?
Don't you have any other backup, from a sammy rom, that should restore your efs,
Two days ago happened to me the same thing.
What I've done was
1. Flash the Pit file from the leaked 4.4.2
2. Restore a backup from a 4.1.2 Sammy rom
3. Full wipe in recovery. Efs error was gone
4. Restore the backup again and boot up.
5. Update the recovery
6. Wipe again
7. Flashed the Gnabo Rom V5
Now everything it's working pretty damn good.
Hope you can solve the issue.
jika23 said:
Don't you have any other backup, from a sammy rom, that should restore your efs,
Two days ago happened to me the same thing.
What I've done was
1. Flash the Pit file from the leaked 4.4.2
2. Restore a backup from a 4.1.2 Sammy rom
3. Full wipe in recovery. Efs error was gone
4. Restore the backup again and boot up.
5. Update the recovery
6. Wipe again
7. Flashed the Gnabo Rom V5
Now everything it's working pretty damn good.
Hope you can solve the issue.
Click to expand...
Click to collapse
Where exactly is the PIT file I should be looking for? Been looking for a while now.
I got bored of my now aging Samsung Galaxy tab 2 10.1 and decided to try and flash it to CM 10.1 . in hopes of a speed boost. I had never flashed before But these are the steeps i followed.
First i rooted device through Kingo Root aplication, No problems there.
Then i got Odin Mobile from the app store . I put these 3 files on my device .
E4GT-EL29-directbootCWM-v3.tar.md5
CM 10.1 ROM 4.2.2 JB
CM 10.1 Gapps zip
taken from here **cant post link as i am a new member**
Then in ODIN Mobile in the section that says kernal i loaded the first file and clicked flash firmware. But instead of rebooting into clock work recovery (which is what i think was meant to happen??) the tablet rebooted and then stalled on the Samsung logo, where it remained, even if i reboot . Samsung comes up on screen and it stays there.
i can reboot into what i think is recovery mode where i have some options i tried selecting "wipe data/factory reset" but the problem still persisted .
I have no idea how to proceed from here. Can someone please help me recover my tablet to its original state.
Thanks
ronanbrowne88 said:
I got bored of my now aging Samsung Galaxy tab 2 10.1 and decided to try and flash it to CM 10.1 . in hopes of a speed boost. I had never flashed before But these are the steeps i followed.
First i rooted device through Kingo Root aplication, No problems there.
Then i got Odin Mobile from the app store . I put these 3 files on my device .
E4GT-EL29-directbootCWM-v3.tar.md5
CM 10.1 ROM 4.2.2 JB
CM 10.1 Gapps zip
taken from here **cant post link as i am a new member**
Then in ODIN Mobile in the section that says kernal i loaded the first file and clicked flash firmware. But instead of rebooting into clock work recovery (which is what i think was meant to happen??) the tablet rebooted and then stalled on the Samsung logo, where it remained, even if i reboot . Samsung comes up on screen and it stays there.
i can reboot into what i think is recovery mode where i have some options i tried selecting "wipe data/factory reset" but the problem still persisted .
I have no idea how to proceed from here. Can someone please help me recover my tablet to its original state.
Thanks
Click to expand...
Click to collapse
U just need to boot into recovery and flash cm10 and gapps from there after wiping system, data, dalvic cache and cache. These r the steps for CWM.
E4GT -EL29 CWM doesn't sound like a file that is for this tablet, it has to do with a Samsung phone.
Recheck your info and if possible post where you got this file from.
If you flashed the wrong file your tablet could be toast.
Pp.
Hello guys. I recently flashed TWRP on my s6 using Odin. The first time I did it, it said that I successfully flashed it but I had autoreboot ticked, so I tried to check if my recovery has changed but it was still the stock recovery. So I tried to flash it again now without the autoreboot. It got stuck to the downloading screen even though odin has already finished. So I tried to force shutdown the phone. I tried to go to the recovery again and it was successfully flashed. I installed a new Custom rom and the Gapps (made sure I wipe everything before flashing), cleared the cached and tried to reboot. But to my surprise it was stuck to the TWRP. When I try to boot to system it's just stuck on the Galaxy s6 powered by android.
I'm sure I had the right trwp file and such but I might have made a mistake somewhere. I don't really know. Help guys?
My phone is the Canadian version G920W8
what ROM are you trying to install?
did check if your device is supported before flashing?