Hi i kind of bricked my Mediapad 7 when tring to update Cyangen 10.2 to Cyangen 11. Need some help how to proceed.
First i booted into TWRP and tried to install the file
S7-301u V100R002C232B005 ICS Android 4.0.3 General Version.zip
to go back from Cyano 10.2 to stock rom 4.0.3. But this failed.
So i directly installed
cm-11-20140118-UNOFFICIAL-hws7300u.zip
Installation went OK. No, i didn't do a backup of the installed 10.2.
After reboot, the device is not booting but always going back to TWRP. What can i do?
What i tried in TWRP so far:
Reinstalling cm-11-20140118-UNOFFICIAL-hws7300u.zip
Reinstalling cm-10.1-20130526-UNOFFICIAL-hws7300u.zip
Wipe Cache
Factory Reset
Nothing helps. Always booting into TWRP v2.3.2.3 :crying:
Thanx for any help how to resolve this!
Forgot: During install of firmware there is a log-line:
E. Unknown File System: 'datamedia'
no slash between data and media
Solved
Solved it.
- Went back to stock recovery with "Auto_recovery_installer_for_huawei_mediapad"
- installed 4.0.3
- then installes cyanogen 11 with twrp
pillepalle555 said:
Solved it.
- Went back to stock recovery with "Auto_recovery_installer_for_huawei_mediapad"
- installed 4.0.3
- then installes cyanogen 11 with twrp
Click to expand...
Click to collapse
I had the problem of not being able to reinstall a stock rom as well.
How EXACTLY did you do it for the stock one?
I've also found out from a CM developer that stock roms can't be installed with the custom recoveries like TWRP or CWM.
Which is a nice thing to know since there doesn't seem to be any info on the forums about that.
Related
------------- SOLVED! --------------
Hello all,
First of all I want to say I'm pretty new to flashing ROMs etc.
Currently I'm at stock 4.3 Jellybean and I want to flash my SGS3 to the new CM 11 ROM.
I rooted my phone following this tutorial: vvvvvv.telefoonrooten.nl/samsung/samsung-galaxy-s3-root/ (sorry if its in Dutch, but it uses the CF-Root-SGS3-v6.3 and Odin).
After I rooted I copied both the CM11 ROM and GAPPS to my external SD, I went to recovery and tried to install the new custom ROM but I got an error (status 7) and it was aborted.
Also if I try to reboot it won't boot normally as it should be but it goes back to recovery mode automatically...
I fixed to get back to Jellybean by flashing the stock rom (unrooting?) it via Odin.
Anyone else got the exact same problem as I do and knows a solution to be able to flash CM 11?
Thanks in advance,
Steelbear
Steelbear said:
Anyone else got the exact same problem as I do and knows a solution to be able to flash CM 11?
Click to expand...
Click to collapse
please read the thirst post in a rom/kernel/whatever thread. and maybe if you havent done it already you should also read the stickies in general section.
FAQ (Read before post !!)
- If you obtain Error 7 when you tried to install ROM in CWM or TWRP
Install the latest version of CMW or TWRP
Click to expand...
Click to collapse
BTW latest philz touch recovery works too
Since you went back to stock and you already know how to root, I suggest you go to Play Store and download ROM Manager to help you install latest CWM recovery on your device.
Or you can simply go to CWM website, pick the version of the recovery for your phone and flash it via Odin.
Hope it helps.
Steelbear said:
Hello all,
First of all I want to say I'm pretty new to flashing ROMs etc.
Currently I'm at stock 4.3 Jellybean and I want to flash my SGS3 to the new CM 11 ROM.
I rooted my phone following this tutorial: vvvvvv.telefoonrooten.nl/samsung/samsung-galaxy-s3-root/ (sorry if its in Dutch, but it uses the CF-Root-SGS3-v6.3 and Odin).
After I rooted I copied both the CM11 ROM and GAPPS to my external SD, I went to recovery and tried to install the new custom ROM but I got an error (status 7) and it was aborted.
Also if I try to reboot it won't boot normally as it should be but it goes back to recovery mode automatically...
I fixed to get back to Jellybean by flashing the stock rom (unrooting?) it via Odin.
Anyone else got the exact same problem as I do and knows a solution to be able to flash CM 11?
Thanks in advance,
Steelbear
Click to expand...
Click to collapse
I had the same problem the fix is quite easy
flash the latest CWM 6.0.4.4 and flash cm11 it will work fine
Blackwolf10 said:
I had the same problem the fix is quite easy
flash the latest CWM 6.0.4.4 and flash cm11 it will work fine
Click to expand...
Click to collapse
Indeed it worked! I found it out myself yesterday. Went to the CWM site and downloaded the latest version (6.0.4.4.) and flashed it through Odin. But thanks for your input anyways (to all who replied) !
An alternative solution that I often use is to open the Updater Script in META-INF folder in the ROM's zip and delete first lines, where it gets device model as property.
Obviously it's an UNSAFE operation (because that lines avoid to install ROMs of other phone on mine) but when I'm sure that ROM I've downloaded is for my phone I do it and it works
New too this whole phone, but I've rooted & ROM'd the Kindle Fire (Gen 1.) Samsung Galaxy S3, LG Vortex, and a few other devices so I'm not stupid when it comes too this stuff.
I've never been a fan of CWM, but anyways I used the AIO Vibrant Toolbox too root it, then I added a recovery with the Custom ROM Button, selected the zip and it *Eventually* got me int CWMR v2.5.0.4, I downloaded c-Rom, and http://forum.xda-developers.com/showthread.php?t=2535547, I tried both but they each fail with
"Installing Update...
E: Error in /sdcard/ROM.zip
(Status 0)
Installation Aborted"
I wiped Dalvik, Factory Reset, Wiped Cache, eevrything. But nothing seems too have worked.
Same problem
Hi I'm currently having the same problem and I also have experience rooting other devices with no problem. I even re rooted the device from the beginning and still a no go. If anyone has any solution to our problems please reply thanks.
Bumping, any help available?
depends on what version of android your'e running, i'm assuming 2.2 since you just rooted it. so grab a cm7, cm 10.2, cm11 or any 4.4.2 rom and a 4.4.2 kernel as well. first flash cm7 and let it fully boot into the os, afterwards boot back into recovery and flash cm 10.2 same as before let it boot, now flash that 4.4.2 kernel and while in same recovery session choose "reboot recovery" option now go ahead and flash what ever kitkat rom you like...
Actually I rooted mine to stock eclair from 2.2. I wasn't sure if I needed to stay because all the guides showed to go to 2.1. It is currently rooted with stock rom and I haven't been able to get further than that.
v4vamp said:
Actually I rooted mine to stock eclair from 2.2. I wasn't sure if I needed to stay because all the guides showed to go to 2.1. It is currently rooted with stock rom and I haven't been able to get further than that.
Click to expand...
Click to collapse
try what i mentioned in my previous comment, it should get your device up to date.
Hey Guys,
I'm having a bit of an issue. Currently I was running STOCK Android 4.3 JB, have been for a while, it started to get a bit slow & I was wanting to fresh install, but also try out a 5.0 lollipop ROM. I've rooted my phone in the past and installed custom ROMs before without a problem (Revolution Remix + Cyanogenmod 11), however, I decided to try Liquidsmooth 5.0 lollipop. i followed this video,
https://www.youtube.com/watch?v=QquFDFEEKlI
http://forum.xda-developers.com/galaxy-s3/development/rom-liquidsmooth-lollipop-4-0-b1-t2980477
I downloaded both files and copied them onto my MicroSD card.
I backed up my data (contacts, images, files etc..)
Booted into "Recovery Mode", wiping Cache & factory Reset
When to install from SD, located file and it started reading/installing (sorry can't remember exactly what it did), but during process it failed. I went back into Android (had to setup again), Went and made sure Developer Mode and USB Debugging was on, still didn't work.
Went to make sure CWM was installed/update, which it said it was (possibly from previous custom installs?), tried updating, failed. It said
Went and installed 'SuperSU' from Play store, but got this error.
Decided to try re-install STOCk 4.3 JB, I
made sure USB Debugging was on
loaded Odin 3.07 (or was it 3.09) and loaded 4.3 Firmware under PDA (left everything else as is)
Started and let it do its thing. It finished/PASSED and phone restarted.
i went back into the phone, installed ROM manager & SuperSU again to give it another shot... but same problem again, getting the error above.
I'm not sure what's happened and I'm not sure what "solutions" to search for... anyone have any suggestions?
At this stage I'm thinking of just going back to STOCK 4.3, then maybe try again (either with Liquidsmooth lollipop, or, Slimkat 4.4)
Thanks guys, any help would be super appreciated,
Regards,
~ Dave
Le Widget said:
Hey Guys,
I'm having a bit of an issue. Currently I was running STOCK Android 4.3 JB, have been for a while, it started to get a bit slow & I was wanting to fresh install, but also try out a 5.0 lollipop ROM. I've rooted my phone in the past and installed custom ROMs before without a problem (Revolution Remix + Cyanogenmod 11), however, I decided to try Liquidsmooth 5.0 lollipop. i followed this video,
https://www.youtube.com/watch?v=QquFDFEEKlI
http://forum.xda-developers.com/galaxy-s3/development/rom-liquidsmooth-lollipop-4-0-b1-t2980477
I downloaded both files and copied them onto my MicroSD card.
I backed up my data (contacts, images, files etc..)
Booted into "Recovery Mode", wiping Cache & factory Reset
When to install from SD, located file and it started reading/installing (sorry can't remember exactly what it did), but during process it failed. I went back into Android (had to setup again), Went and made sure Developer Mode and USB Debugging was on, still didn't work.
Went to make sure CWM was installed/update, which it said it was (possibly from previous custom installs?), tried updating, failed. It said
Went and installed 'SuperSU' from Play store, but got this error.
Decided to try re-install STOCk 4.3 JB, I
made sure USB Debugging was on
loaded Odin 3.07 (or was it 3.09) and loaded 4.3 Firmware under PDA (left everything else as is)
Started and let it do its thing. It finished/PASSED and phone restarted.
i went back into the phone, installed ROM manager & SuperSU again to give it another shot... but same problem again, getting the error above.
I'm not sure what's happened and I'm not sure what "solutions" to search for... anyone have any suggestions?
At this stage I'm thinking of just going back to STOCK 4.3, then maybe try again (either with Liquidsmooth lollipop, or, Slimkat 4.4)
Thanks guys, any help would be super appreciated,
Regards,
~ Dave
Click to expand...
Click to collapse
First of all and most important don't use rom manager! it causes more problems than anything else.The best way to install custom roms is to use Cwm,PhilZ or Twrp to install anything!
Flash superSU zip in recovery from here >> http://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip?retrieve_file=1 << SuperSU forum here >> http://forum.xda-developers.com/showthread.php?t=1538053 << Technically you should not need to flash SuperSU because nearly all custom roms come with root built in so you could flash a custom recovery then wipe and flash your rom (but I can see you have been having problems doing that)
What you should do is
(1) Flash a custom recovery with Odin (Recommend PhilZ)
(2) Reboot to custom recovery
(3) Wipe phone
(4) Install custom rom (which is already rooted) from Ext SD card
(5) Reboot (If you get bootloop factory reset/ wipe cache
Also to note PhilZ recovery (which I think is better as more options and is based on Cwm) as a option to fix root in settings.
tallman43 said:
First of all and most important don't use rom manager! it causes more problems than anything else.The best way to install custom roms is to use Cwm,PhilZ or Twrp to install anything!
Flash superSU zip in recovery from here >> http://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip?retrieve_file=1 << SuperSU forum here >> http://forum.xda-developers.com/showthread.php?t=1538053 << Technically you should not need to flash SuperSU because nearly all custom roms come with root built in so you could flash a custom recovery then wipe and flash your rom (but I can see you have been having problems doing that)
What you should do is
(1) Flash a custom recovery with Odin (Recommend PhilZ)
(2) Reboot to custom recovery
(3) Wipe phone
(4) Install custom rom (which is already rooted) from Ext SD card
(5) Reboot (If you get bootloop factory reset/ wipe cache
Also to note PhilZ recovery (which I think is better as more options and is based on Cwm) as a option to fix root in settings.
Click to expand...
Click to collapse
hi tallman, much appreciated for the reply
For some reason I couldnt get Philz Custom Recovery to work with odin, kept getting an error :/ . So I ended up trying TWRP, which worked, I booted into it then installed Liquidsmooth + gapps, all installed ok, but all up it was the same process you mentioned, which I greatly appreciate.
So running Liquidsmooth 5 now with TWRP recovery, though will likely give Philz recovery a shot down the track
Le Widget said:
hi tallman, much appreciated for the reply
For some reason I couldnt get Philz Custom Recovery to work with odin, kept getting an error :/ . So I ended up trying TWRP, which worked, I booted into it then installed Liquidsmooth + gapps, all installed ok, but all up it was the same process you mentioned, which I greatly appreciate.
So running Liquidsmooth 5 now with TWRP recovery, though will likely give Philz recovery a shot down the track
Click to expand...
Click to collapse
Good to hear it's working Yes it's worth persevering with PhilZ it's a good recovery although Twrp is not bad either:good:
Hello,
I have SGS3 i9300 that was installed on it Cyanogenmod 11 for along time and it working great!!
until i did some mistake because i have a problem with the power button and i thought it was the CM that cause this resets.... but now it's too late/
i fix the problem and tried to install CM11 back, but the phone showing black screen after the Samasung s3 logo... and nothing.
the steps that i try is:
1. install recover CWM and install ROMs.
2. install recover TWRP and install ROMs.
3. install Stock Rom from Odin.
4. install CM10 snapshot or CM11 nightly.
5. binary code reset.
6. install throw CM windows installer.
7. install BlissPop.
none of the above works :crying:
the only ROM that i manage to install where "Android Revolution HD 29.0"
PLEASE HELP ME....
thanks
were you running a custom kernel also?
Phantogenic said:
were you running a custom kernel also?
Click to expand...
Click to collapse
i don't know
but i do install Stock Rom
Does it not change to the Stock Kernel?
UP
up please i still get my phone work
i recently install stock rom 4.0.2
and this work but when i do upgrade with Kies or even Odin to new version
i get this problem with the black screen immediately after the Smasung S3 logo :crying:
please help
Hello,
i need your help.
I flashed the latest update for the Galaxy Tab S6 with android 11. I fully wiped everything and i want to root my device again. (was already rooted in Android 10)
TWRP has now a offical Recovery Support so i flashed this one instead of the unoffical one.
Worked well and booted directly into Recovery after flash.
I did the common things: format the /data partition, system’ partition is unmounted
Then i flashed the Encryption-disabler file first, then WETA_Kernel_T860-7.0_TF2 and then Magisk.
After that i rebooted my device, but somehow my device is stucking in a loop now.
Do i need any wipe?
Is android 11 the issue?
Is the WETA Kernel 7.0 not compaible with Android 11?
I dont know what i do wrong honestly. I did the same thing, when i updated to android 10 and everything there works
Any help is appreacited.
Thanks in Advance
kadir456 said:
Hello,
i need your help.
I flashed the latest update for the Galaxy Tab S6 with android 11. I fully wiped everything and i want to root my device again. (was already rooted in Android 10)
TWRP has now a offical Recovery Support so i flashed this one instead of the unoffical one.
Worked well and booted directly into Recovery after flash.
I did the common things: format the /data partition, system’ partition is unmounted
Then i flashed the Encryption-disabler file first, then WETA_Kernel_T860-7.0_TF2 and then Magisk.
After that i rebooted my device, but somehow my device is stucking in a loop now.
Do i need any wipe?
Is android 11 the issue?
Is the WETA Kernel 7.0 not compaible with Android 11?
I dont know what i do wrong honestly. I did the same thing, when i updated to android 10 and everything there works
Any help is appreacited.
Thanks in Advance
Click to expand...
Click to collapse
Where did you get android 11 from? I've been waiting for this