Related
Recently I hard-bricked my Tab whilst installing a Rom on it (Brick Bug). Now I have a replacement, and it's about time I replaced the HC with something else.
I plan to use the 'Singha ROM ICS P6800DXLP7' ROM and ' Dedraks' GT-P6800' kernel. I'm guessing installation for both is via CWM, but that is how I bricked my tab last time. How can I work around this as to not brick it again? Odin? Which do I install first? Any guidance would really be appreciated!
Thanks
Which cwm you using that cause it to brick?
Share some detail procedure...wipe on stock rom, custom rom, kernel...etc which end with brick?
For now I believe safe atm..
- From stock ICS
- Root with this method: http://forum.xda-developers.com/showthread.php?t=1849235
- Install cwm using Mobile Odin
- Boot to cwm recovery
- Flash custom rom and custom kernel
- Reboot recovery NOT reboot system.
- Full wipe and fix permission
- Reboot system to home screen
That what I always do
Here's what works for me
first, d/l CWM to SD card.
then power down.
reboot into download mode ,PC Odin is my install of choice for the roms...
then power down again after the new rom installs and re-boots
re-boot into recovery and choose install zip from SD and choose CWM (which is a temporary install)
dont wipe anything, just choose to install zip and then choose your new kernel.
After kernel (a safe one) installs, then re-boot system.
Ive never bricked this tab or my GN7000 Note
good luck
correct me if im wrong, but as long as you do not factory reset in stock ics recovery you are okay. Right?
Some Note GT 7000 guys reported that they bricked their phablets by copping large files (being on ICS). If this doesn't affect our P6800s, then you are not wrong.
I had installed LQ2 without wiping anything. But had many Screen Offs and Shut Downs, so I considered to risk the clean install.
Did it with Mobile Odin Pro, but first
Ensured that I already have CWM 6.0.0.1
Flashed Dedraks Kernel.
In Mobile Odin chosen "open file..." and then the particular md5 file,
BUT EXCLUDED:
1. Kernel
2. Recovery
Then I selected "wipe" and "clean", crossed my fingers and everything went OK.
Not quite everything, because I lost root, although I am pretty sure that I did not unselect "everroot'.
It was not a big issue. Installed again "root.zip" via CWM recovery.
Its about a week since then and I have nothing to complain.
...
Thanks for the responses guys.
Does this sound safe?:
Flash LQ2 via PC Odin
Root from universal recovery
Flash CWM 6.0.11 via PC Odin
Flash Dedraks Kernel via CWM
Then root again if needed.
Thanks
rumpypumpy said:
Thanks for the responses guys.
Does this sound safe?:
Flash LQ2 via PC Odin
Root from universal recovery
Flash CWM 6.0.11 via PC Odin
Flash Dedraks Kernel via CWM
Then root again if needed.
Thanks
Click to expand...
Click to collapse
Yeah, with these steps you should be safe.
Happy flashing
Hi guys,
I've been thinkin about selling my TF101g and buy a new model, but my tablet has custom recovery and Rom, and I would like turn it all stock, and i couldn't find any thread to the Tf101g.
Can somebody help me with a thread that works?
lennao said:
Hi guys,
I've been thinkin about selling my TF101g and buy a new model, but my tablet has custom recovery and Rom, and I would like turn it all stock, and i couldn't find any thread to the Tf101g.
Can somebody help me with a thread that works?
Click to expand...
Click to collapse
Hi, I'm new to this forum (first post).
I had the same problem - e.g. I wanted to return to stock. I flashed ' PERI 1-click recovery' and the latest version of Revolver custom ROM for the TF101G but I couldn't get 3G to work (unknown Baseband), and PERI wouldn't let me flash the stock ROM - it gave an error 'assert failed' 'Status 7'.
Thought I'd b*****d it thoroughly and couldn't find a thread telling me how to get back to Stock, but trial and error prevailed.
This is what I did (assume you already have ROOT and a custom recovery installed):
1. Download the latest ASUS stock ROM zip from the ASUS site to the PC. Make sure you select the right one for your model (mine's the WW TF101G version)
http://support.asus.com/Download.aspx?SLanguage=en&m=Eee+Pad+Transformer+TF101G&p=20&s=16
2. For some reason ASUS put the stock ROM zip image inside another zip file, so extract it from the downloaded zip file and copy the extracted stock ROM zip (e.g. WW_epad-user-9.2.2.6.zip) to TF101G Internal Storage (not an external SD)
3. The custom recovery you have installed my allow you to flash the stock ROM, in which case just do steps 7 and then 10 onwards. Mine (PERI) gave me an Assert Failed error, in which case ....
4. Download ClockWork Recovery for the Transformer. I used Clockwork_Recovery_5.8.1.8_by_JvS_Corp_V3 from this site and it worked just fine. I don't know which other versions work and which don't:
http://forum.xda-developers.com/showthread.php?t=1577929
5. Copy the downloaded Clockwork_Recovery_5.8.1.8_by_JvS_Corp_V3.zip to TF101G Internal Storage (not external SD)
6. Now boot the TF101G into recovery mode (Power + Volume Down until prompt appears, then Volume Up for recovery)
7. Wipe all caches (including the user data cache)
8. Flash Clockwork_Recovery_5.8.1.8_by_JvS_Corp_V3.zip - you'll see lots of scrolling @@@@@@@s, don't worry that's normal
9. Once the Install is complete, Boot into recovery mode again - you should now be in Clockwork Recovery V5.8.1.8
10. Flash the stock ROM (e.g. WW_epad-user-9.2.2.6.zip). Wait until the install is complete.
11. Reboot normally. You will see a blue status bar which will take a while to complete and then it will reboot itself, you may see a message 'Android is Updating' which will also take a while to complete.
After doing this, you should now have the stock ROM, stock recovery, no ROOT and you will be asked to set up the Tablet for the first time, i.e. back to stock.
P.S. If you don't wipe the User Data cache, you can flash to stock without using your apps / settings / data.
Hope this helps.
i dont understand. If youre going to sell the tf101 why not load it up with custom overclockable kernel, new JB rom, and a custom touch recovery? those are added features compared to a lame stock version of the transformer.
serafis said:
Hi, I'm new to this forum (first post).
I had the same problem - e.g. I wanted to return to stock. I flashed ' PERI 1-click recovery' and the latest version of Revolver custom ROM for the TF101G but I couldn't get 3G to work (unknown Baseband), and PERI wouldn't let me flash the stock ROM - it gave an error 'assert failed' 'Status 7'.
Thought I'd b*****d it thoroughly and couldn't find a thread telling me how to get back to Stock, but trial and error prevailed.
This is what I did (assume you already have ROOT and a custom recovery installed):
1. Download the latest ASUS stock ROM zip from the ASUS site to the PC. Make sure you select the right one for your model (mine's the WW TF101G version)
http://support.asus.com/Download.aspx?SLanguage=en&m=Eee+Pad+Transformer+TF101G&p=20&s=16
2. For some reason ASUS put the stock ROM zip image inside another zip file, so extract it from the downloaded zip file and copy the extracted stock ROM zip (e.g. WW_epad-user-9.2.2.6.zip) to TF101G Internal Storage (not an external SD)
3. The custom recovery you have installed my allow you to flash the stock ROM, in which case just do steps 7 and then 10 onwards. Mine (PERI) gave me an Assert Failed error, in which case ....
4. Download ClockWork Recovery for the Transformer. I used Clockwork_Recovery_5.8.1.8_by_JvS_Corp_V3 from this site and it worked just fine. I don't know which other versions work and which don't:
http://forum.xda-developers.com/showthread.php?t=1577929
5. Copy the downloaded Clockwork_Recovery_5.8.1.8_by_JvS_Corp_V3.zip to TF101G Internal Storage (not external SD)
6. Now boot the TF101G into recovery mode (Power + Volume Down until prompt appears, then Volume Up for recovery)
7. Wipe all caches (including the user data cache)
8. Flash Clockwork_Recovery_5.8.1.8_by_JvS_Corp_V3.zip - you'll see lots of scrolling @@@@@@@s, don't worry that's normal
9. Once the Install is complete, Boot into recovery mode again - you should now be in Clockwork Recovery V5.8.1.8
10. Flash the stock ROM (e.g. WW_epad-user-9.2.2.6.zip). Wait until the install is complete.
11. Reboot normally. You will see a blue status bar which will take a while to complete and then it will reboot itself, you may see a message 'Android is Updating' which will also take a while to complete.
After doing this, you should now have the stock ROM, stock recovery, no ROOT and you will be asked to set up the Tablet for the first time, i.e. back to stock.
P.S. If you don't wipe the User Data cache, you can flash to stock without using your apps / settings / data.
Hope this helps.
Click to expand...
Click to collapse
thx man, i'll try this at home tonight!!
haxin said:
i dont understand. If youre going to sell the tf101 why not load it up with custom overclockable kernel, new JB rom, and a custom touch recovery? those are added features compared to a lame stock version of the transformer.
Click to expand...
Click to collapse
because it doesn't exist a JB ROM with 3G working, and usually, when i'll sell something, i prefer selling with the stock image, it's more guarantee that will work properly, like when leaving the store, so they can root and change roms themselves.
lennao said:
thx man, i'll try this at home tonight!!
Click to expand...
Click to collapse
In my post, where I said "P.S. If you don't wipe the User Data cache, you can flash to stock without using your apps / settings / data", I meant "...without losing your apps / settings / data". That way you can carry on using it until you sell it, and then just do a factory reset once you have a buyer.
Good luck.
serafis said:
In my post, where I said "P.S. If you don't wipe the User Data cache, you can flash to stock without using your apps / settings / data", I meant "...without losing your apps / settings / data".
Good luck.
Click to expand...
Click to collapse
hey,
i would like to thank you, your tutorial works fine! and was pretty easy too, nothing complicated.
thx again!
lennao said:
hey,
i would like to thank you, your tutorial works fine! and was pretty easy too, nothing complicated.
thx again!
Click to expand...
Click to collapse
Excellent, glad it worked out.
Procedure if you ARE NOT running baseband JYUS06032013 (ICS Basebands) :
boot ICS CWM
flash FLEX-JB-JYUS06032013-FIRMWARE.zip from CWM
format system in CWM (will NOT wipe data, but makes sure old rom does not flash back stock recovery)
restart start recovery/adb reboot recovery (JB CWM is installed - do not try to fastboot boot ICS CWM)
flash FLEX-JB-JYUS06032013-ROM.zip from CWM.
reboot
Procedure if you ARE running baseband JYUS06032013 (JB Baseband) :
get root (Instructions HERE - use GANDALF)
install CWM (Instructions HERE)
flash FLEX-JB-JYUS06032013-FIRMWARE.zip from CWM
format system in CWM (will NOT wipe data, but makes sure old rom does not flash back stock recovery)
reboot to CWM
flash FLEX-JB-JYUS06032013-ROM.zip from CWM.
reboot
This ROM is Pantech stock stock stock with no mods other than CWM installation protection and all stock permissions and symlinks carefully maintained and consistent with the product of a successful OTA. It runs well with nothing broken. You MUST be on JB firmware (below) to run it properly.
The firmware is also stock, with the exception of the open aboot allowing fastboot boot <bootimage>, and installation of JB CWM with nothing else added or changed.
You can let the new CWM root it if you like when you exit - it will prompt you.
Downloads:
md5: 1a0ca5f177bce2f4c428931616e0ecd1 FLEX-JB-JYUS06032013-FIRMWARE.zip
md5: 17c0e611ab6dfbca230571c1e40f3d14 FLEX-JB-JYUS06032013-ROM.zip
Code:
[B]GPL INFO[/B]
The kernel used in the ROM is the unaltered, stock rom
and boot image provided by the Pantech OTA.
The kernel used in CWM provided I built from unaltered
Pantech provided source code.
The source code for both kernels can be obtained on the
[URL="http://opensource.pantech.com/"]Pantech Open Source[/URL] website.
:good::good::good::good::good::good::good:
much appreciated. i am dreaming of it will do it tonight and post the result.
attn1 said:
Procedure if you ARE NOT running baseband JYUS06032013 (ICS Basebands) :
boot ICS CWM
flash FLEX-JB-JYUS06032013-FIRMWARE.zip from CWM
format system in CWM (will NOT wipe data, but makes sure old rom does not flash back stock recovery)
restart start recovery/adb reboot recovery (JB CWM is installed - do not try to fastboot boot ICS CWM)
flash FLEX-JB-JYUS06032013-ROM.zip from CWM.
reboot
Procedure if you ARE running baseband JYUS06032013 (JB Baseband) :
get root (Instructions HERE - use GANDALF)
install CWM (Instructions HERE)
flash FLEX-JB-JYUS06032013-FIRMWARE.zip from CWM
format system in CWM (will NOT wipe data, but makes sure old rom does not flash back stock recovery)
reboot to CWM
flash FLEX-JB-JYUS06032013-ROM.zip from CWM.
reboot
This ROM is Pantech stock stock stock with no mods other than CWM installation protection and all stock permissions and symlinks carefully maintained and consistent with the product of a successful OTA. It runs well with nothing broken. You MUST be on JB firmware (below) to run it properly.
The firmware is also stock, with the exception of the open aboot allowing fastboot boot <bootimage>, and installation of JB CWM with nothing else added or changed.
You can let the new CWM root it if you like when you exit - it will prompt you.
Downloads:
md5: 1a0ca5f177bce2f4c428931616e0ecd1 FLEX-JB-JYUS06032013-FIRMWARE.zip
md5: 17c0e611ab6dfbca230571c1e40f3d14 FLEX-JB-JYUS06032013-ROM.zip
Code:
[B]GPL INFO[/B]
The kernel used in the ROM is the unaltered, stock rom
and boot image provided by the Pantech OTA.
The kernel used in CWM provided I built from unaltered
Pantech provided source code.
The source code for both kernels can be obtained on the
[URL="http://opensource.pantech.com/"]Pantech Open Source[/URL] website.
Click to expand...
Click to collapse
after a few days to stay with this JB on my flex. i found big problem with WIFI connectivity:
1 - connect and used about 10 to 30mn,, it is still connected but no internet.
2 - reconnect -> authentication problem.
3 - reboot a fews time to make wifi back to work.
4 - back to problem number 1
5 - Camera App still randomly cant be used unless restart. ( same problem since ICS )
6 - some intensive graphic games cause reboot the phone, eg Clash of Clans ( new in this JB)
What is good about JB is feel smooth and faster.
Any help, please?
Thanks @attn1! Works great.
Sent from my PantechP8010 using Tapatalk
tangbunna said:
after a few days to stay with this JB on my flex. i found big problem with WIFI connectivity:
1 - connect and used about 10 to 30mn,, it is still connected but no internet.
2 - reconnect -> authentication problem.
3 - reboot a fews time to make wifi back to work.
4 - back to problem number 1
5 - Camera App still randomly cant be used unless restart. ( same problem since ICS )
6 - some intensive graphic games cause reboot the phone, eg Clash of Clans ( new in this JB)
What is good about JB is feel smooth and faster. My wifi works fine, and the camera works fine.
Any help, please?
Click to expand...
Click to collapse
Try flashing my firmware package again, then flashing the ROM again. If you still have these issues, then wipe data/factory reset from clockworkmod. This is working for everyone else reporting, including me.
THIS work on Motorola defy
ela1103 said:
THIS work on Motorola defy
Click to expand...
Click to collapse
highly unlikely to impossible in this version of reality.
Look at mac address of both phone. They are the same. And both phone connected to the same ip of a router.
Even i use 2 routers, and connect one each, they seems to drop connection very often.
Unless a phone turn wifi off to let other one stay in good connection.
Do you have another alternative firmware file? So it could have different mac address ?
tangbunna said:
Look at mac address of both phone. They are the same. And both phone connected to the same ip of a router.
Even i use 2 routers, and connect one each, they seems to drop connection very often.
Unless a phone turn wifi off to let other one stay in good connection.
Do you have another alternative firmware file? So it could have different mac address ?
Click to expand...
Click to collapse
Looks like you restored the same /data backup to each phone. MAC address is determined by your wifi hardware, not this firmware.
attn1 said:
Looks like you restored the same /data backup to each phone. MAC address is determined by your wifi hardware, not this firmware.
Click to expand...
Click to collapse
I did not restore anything. While both phones on ics they both worked fine without duplicated mac address issue. Then i followed the instruction of the 2 files for upgrade to jelly bean. I didnt do any back up or restore. Just flash the firmware zip then jb rom zip the. Everything of my data are still there wifi are working fine untill i flash another phone to jelly bean too, both phone must have one wifi to turn off to make another one's wifi works fine.
Do you have the flex and upgraded to jelly bean by this two files? Could you tell me your mac address of your wifi ?
tangbunna said:
I did not restore anything. While both phones on ics they both worked fine without duplicated mac address issue. Then i followed the instruction of the 2 files for upgrade to jelly bean. I didnt do any back up or restore. Just flash the firmware zip then jb rom zip the. Everything of my data are still there wifi are working fine untill i flash another phone to jelly bean too, both phone must have one wifi to turn off to make another one's wifi works fine.
Do you have the flex and upgraded to jelly bean by this two files? Could you tell me your mac address of your wifi ?
Click to expand...
Click to collapse
Apologies. I've verified the problem, have traced it to mmcblk0p10, and here's a fix for you that changes the MAC by one:
Flash this from CWM:
md5: 4e7940c1b5d3690e0e38b083f224a7f1 OSCAR-WIFI-MACFIX.zip
NOTES:
This problem is because the hardware MAC is stored in that partition and read by the wifi firmware. It should never present a problem for people unless they have more than one Flex running this update on the same local area network subnet.
The MAC address starts in mmcblk0p10 at hex offset 30204, and an image file of this partition can be edited CAREFULLY with a hex editor and copied back to that partition. Doing this wrong may result in a bricked device.
attn1 said:
Apologies. I've verified the problem, have traced it to mmcblk0p10, and here's a fix for you that changes the MAC by one:
Flash this from CWM:
md5: 4e7940c1b5d3690e0e38b083f224a7f1 OSCAR-WIFI-MACFIX.zip
NOTES:
This problem is because the hardware MAC is stored in that partition and read by the wifi firmware. It should never present a problem for people unless they have more than one Flex running this update on the same local area network subnet.
The MAC address starts in mmcblk0p10 at hex offset 30204, and an image file of this partition can be edited CAREFULLY with a hex editor and copied back to that partition. Doing this wrong may result in a bricked device.
Click to expand...
Click to collapse
you are genius man! my wifi now changed from ending e9 to f9. no more duplicated :good::good::good::good::good:.
send me your paypal to my inbox, i will buy you a beer! :highfive:
big thanks and cheers !!!
Flex stuck on logo.
only 25% complete. then said signature verification failed?? pls help. (no cwm. only stock)
shusan said:
only 25% complete. then said signature verification failed?? pls help. (no cwm. only stock)
Click to expand...
Click to collapse
You have not provided enough information for me to help you. What was the detailed sequence of events leading to this. Be precise and make sure you list exactly the packages you flashed.
Flex stuck on logo.
thanks for ur quick reply. i was too sick to answer u. so sorry for late. i tried with sd memory update which show me 25% with stock image then show signature verrificatin failled. al most same result from fastboot. signature verification failed. no connection via ADB. i downloaded almost each and every rom and image i found from xda or other forum result r all same. sorry for my English. best regards
attn1 said:
You have not provided enough information for me to help you. What was the detailed sequence of events leading to this. Be precise and make sure you list exactly the packages you flashed.
Click to expand...
Click to collapse
shusan said:
thanks for ur quick reply. i was too sick to answer u. so sorry for late. i tried with sd memory update which show me 25% with stock image then show signature verrificatin failled. al most same result from fastboot. signature verification failed. no connection via ADB. i downloaded almost each and every rom and image i found from xda or other forum result r all same. sorry for my English. best regards
Click to expand...
Click to collapse
In recovery (cwm), check the md5 of the file on the sdcard against the posted md5 like so:
adb shell md5sum /path/filename
If it's not matching, you will get that error.
If you don't have the shipping ICS aboot, you may be stuck. You can't flash or boot images if you've taken the jb update. You still haven't detailed what you started with and what you have tried to do and where it went wrong, so it's hard to tell you exactly what to do or even if there is anything to do.
Any idea about stock rom? I don't have cwm. Only need to restore using original farmware. P8010 already stuck.
shusan said:
Any idea about stock rom? I don't have cwm. Only need to restore using original farmware. P8010 already stuck.
Click to expand...
Click to collapse
There is no stock firmware from Pantech available. If you messed up and can't boot with the JB bootloader, you are screwed.
attn1 said:
There is no stock firmware from Pantech available. If you messed up and can't boot with the JB bootloader, you are screwed.
Click to expand...
Click to collapse
No stock firmware from Pantech? I thought the firmware in the first post is STOCK? No? What about a caught copy from the OTA from AT&T?
Hi, I have bought a samsung tab 3 sm-t311 in China and since they everything related to google, I rooted it and installed CWM,
I installed this rom here with CWM: http://forum.xda-developers.com/showthread.php?t=2404877
Installation was successful but I get this messages when launching my device:
- setup wizard isn't responding. Do you want to close it?
I close it, then:
- Unfortunately, the process android.process.media has stopped.
I press ok, then:
Unfortunately, Samsung keyboard has stopped.
I press ok then:
- Process system isn't responding. Do you want to close it?
I press ok
And it keeps coming back over and over...
What should I do?
Backup
anthony239 said:
Hi, I have bought a samsung tab 3 sm-t311 in China and since they everything related to google, I rooted it and installed CWM,
I installed this rom here with CWM: http://forum.xda-developers.com/showthread.php?t=2404877
Installation was successful but I get this messages when launching my device:
- setup wizard isn't responding. Do you want to close it?
I close it, then:
- Unfortunately, the process android.process.media has stopped.
I press ok, then:
Unfortunately, Samsung keyboard has stopped.
I press ok then:
- Process system isn't responding. Do you want to close it?
I press ok
And it keeps coming back over and over...
What should I do?
Click to expand...
Click to collapse
try fixing permissions in cwm/twrp ,if it does not help then restore your nandroid backup or ask the rom developer for the problem..
it might help you
roshan77ss said:
try fixing permissions in cwm/twrp ,if it does not help then restore your nandroid backup or ask the rom developer for the problem..
it might help you
Click to expand...
Click to collapse
Hi, thanks for replying. I cannot post in the topic of the rom because I am new on the forum (what I get when I try to post something overthere).
Could you please explain me how to fix the permissions in CWM?
I am a beginner who been trying to fix his tablet for a week now, but I still dont understand everything since I cant put all my time on it... If its not about following tutorials step by step, i am lost...
I also tried the fast team one, without any success, when the rom is installed and the device is rebooted, this time the screen stay blocked on "samsung galaxy tab3" for years!!!
sorry, i meant the fast dream rom
I just tried to Flash three roms from sammobile.com (one from hong-kong, one from spain and one from germany) through Odin.
Everytime I get I click on AP to load the rom on odin, I get this message:"md5 error! Binary is invalid".
Since I have rooted the tablet using odin to instal CWM, when I boot the tablet in download mode, I can see:
- PRODUCT NAME: SM-T311
- CURRENT BINARY: Cusom
- SYSTEM STATUS: Custom
Is it related? Someone help plz...
The question is do i really have to install a new rom, now that the tablet is rooted with CWM on it, can't do any manipulation to allow the chinese rom to accept google playstore etc...
My biggest problem with the chinese rom that comes with it is that i cant install download google playstore, i installed it but everytime i open it, it closes right away. Not google nor other google apps available neither since it was sold in china...
anthony239 said:
Hi, thanks for replying. I cannot post in the topic of the rom because I am new on the forum (what I get when I try to post something overthere).
Could you please explain me how to fix the permissions in CWM?
I am a beginner who been trying to fix his tablet for a week now, but I still dont understand everything since I cant put all my time on it... If its not about following tutorials step by step, i am lost...
Click to expand...
Click to collapse
You should be able to post on ROM forum now(as you've reached 10 posts.
And the fix permissions option should be in 'advanced' section in CWM(not sure, I use TWRP recovery)
The Dork Knight Rises said:
You should be able to post on ROM forum now(as you've reached 10 posts.
And the fix permissions option should be in 'advanced' section in CWM(not sure, I use TWRP recovery)
Click to expand...
Click to collapse
Yea im able to post over there now, thx
backup
anthony239 said:
The question is do i really have to install a new rom, now that the tablet is rooted with CWM on it, can't do any manipulation to allow the chinese rom to accept google playstore etc...
My biggest problem with the chinese rom that comes with it is that i cant install download google playstore, i installed it but everytime i open it, it closes right away. Not google nor other google apps available neither since it was sold in china...
Click to expand...
Click to collapse
dont you have cwm backup? if not then flash stock firmware ,find proper odin flashable packages for your device.
always make backup before flashing any rom.
anthony239 said:
Yea im able to post over there now, thx
Click to expand...
Click to collapse
So, could the devs help??
(<---And you don't need to say thanks and spam the thread, that what the button's for)
The Dork Knight Rises said:
So, could the devs help??
(<---And you don't need to say thanks and spam the thread, that what the button's for)
Click to expand...
Click to collapse
In the end, I just used a previous version of Odin (3.4 instead of 3.9) to flash an original stock rom.
Now the problem is that I have a new CWM that works with the volume up, volume down button, and this menu:
- reboot system now
- apply update from ADB
- apply update from external storage
- zipe data/factory reset
- wipe cache partition
- apply update from cache
Since the rom is not really good, i wanted to flash another one (one of those we just talked about), but the backup i did with the previous CWM i had (Philz Advanced CWM 6.08.90) is nowhere in the tablet anymore (i dont have any sd card) and i dont know how to make a back up with this CWM...
So now the question is how to make a backup with this version of CWM so I can try to flash other roms, or how to get the version that i had before without takin any risk of brickin the device (so i can make another backup and try to flash another)
anthony239 said:
In the end, I just used a previous version of Odin (3.4 instead of 3.9) to flash an original stock rom.
Now the problem is that I have a new CWM that works with the volume up, volume down button, and this menu:
- reboot system now
- apply update from ADB
- apply update from external storage
- zipe data/factory reset
- wipe cache partition
- apply update from cache
Since the rom is not really good, i wanted to flash another one (one of those we just talked about), but the backup i did with the previous CWM i had (Philz Advanced CWM 6.08.90) is nowhere in the tablet anymore (i dont have any sd card) and i dont know how to make a back up with this CWM...
So now the question is how to make a backup with this version of CWM so I can try to flash other roms, or how to get the version that i had before without takin any risk of brickin the device (so i can make another backup and try to flash another)
Click to expand...
Click to collapse
Are you sure the new recovery is CWM and not stock recovery?? If you flashed stock ROM, it should've given you stock recovery again...
(Does it show the CWM hat logo in the background?)
The Dork Knight Rises said:
Are you sure the new recovery is CWM and not stock recovery?? If you flashed stock ROM, it should've given you stock recovery again...
(Does it show the CWM hat logo in the background?)
Click to expand...
Click to collapse
Actually, yea its the stock recovery, so should i reroot the phone to install CWM, make a backup just in case, flash another stock rom which i find better, and then try to flash this one in recovery mode?
anthony239 said:
Hi, I have bought a samsung tab 3 sm-t311 in China and since they everything related to google, I rooted it and installed CWM,
I installed this rom here with CWM: http://forum.xda-developers.com/showthread.php?t=2404877
Installation was successful but I get this messages when launching my device:
- setup wizard isn't responding. Do you want to close it?
I close it, then:
- Unfortunately, the process android.process.media has stopped.
I press ok, then:
Unfortunately, Samsung keyboard has stopped.
I press ok then:
- Process system isn't responding. Do you want to close it?
I press ok
And it keeps coming back over and over...
What should I do?
Click to expand...
Click to collapse
Try fix or patch.
Or come back to stock rom.
anthony239 said:
Actually, yea its the stock recovery, so should i reroot the phone to install CWM, make a backup just in case, flash another stock rom which i find better, and then try to flash this one in recovery mode?
Click to expand...
Click to collapse
Yup, I think you'd better to start over again. Try take a look at this : http://forum.xda-developers.com/showthread.php?t=2401901
It works well for my SM-T311 :good: Then you can reroot and make a backup from TWRP easily.
I also suggest you to take a look at this too : http://forum.xda-developers.com/showthread.php?t=2522091 From there, you can get PhilZ touch recovery based on CWM v.6.0.4.5
anthony239 said:
Actually, yea its the stock recovery, so should i reroot the phone to install CWM, make a backup just in case, flash another stock rom which i find better, and then try to flash this one in recovery mode?
Click to expand...
Click to collapse
That's right, look at @Ferris Cruiser's post above. Should help.
(<---Remember to thank him and me if this helps.:good
Ok, my problem is resolved now.
- I had to use the previous version of Odin (3.4) to flash a rom from sammobile.com
- Then, I rooted the phone, reinstalling CWM philz version
- I did a backup using CWM
- Finally I flashed the custom rom using CWM
Thank u all for helping
anthony239 said:
Ok, my problem is resolved now.
- I had to use the previous version of Odin (3.4) to flash a rom from sammobile.com
- Then, I rooted the phone, reinstalling CWM philz version
- I did a backup using CWM
- Finally I flashed the custom rom using CWM
Thank u all for helping
Click to expand...
Click to collapse
Glad to help! :good:
HELP
I bought a Samsung Galaxy Tab 3 SM-T311 in Mainland China last month and I cannot install google play can anyone help.
Hello guys,
I'm still relatively new to rooting stuff on the Nexus 5 (and 7). Running a rooted stock android 4.4.4. with Franco kernal, but with Lollipop now available.. Of course I want to upgrade. I am looking for a stock android 5 rom with prepoot. Is there a prerooted rom available? And do I have to flash stock kernal first before flashing the rom?
Thanks in advance!
Justin
IVS IVRIS said:
Hello guys,
I'm still relatively new to rooting stuff on the Nexus 5 (and 7). Running a rooted stock android 4.4.4. with Franco kernal, but with Lollipop now available.. Of course I want to upgrade. I am looking for a stock android 5 rom with prepoot. Is there a prerooted rom available? And do I have to flash stock kernal first before flashing the rom?
Thanks in advance!
Justin
Click to expand...
Click to collapse
Not exactly no. L root is different from KitKat. You have to flash a permissive boot.img (kernel) before flashing SuperSU in recovery.
There are flashable zips. There is one linked in the "guides and info" link in my signatrue (see section 6)... But you still need to flash the chainfire or @sykopompos Permissive boot.img
rootSU said:
Not exactly no. L root is different from KitKat. You have to flash a permissive boot.img (kernel) before flashing SuperSU in recovery.
There are flashable zips. There is one linked in the "guides and info" link in my signatrue (see section 6)... But you still need to flash the chainfire or @sykopompos Permissive boot.img
Click to expand...
Click to collapse
Thank you for the quick reply. The rom over here: http://forum.xda-developers.com/goo...-android-4-4-3-ktu84m-rooted-busybox-t2557523 may suit my needs indeed. Although he's saying "-Don't install SuperSU (won't work, must use CF-Auto-Root)"
So, in my situation.. what I should do would be:
Factory reset
Flash rom with TWRP (my recovery)
Flash radio
Use the latest CF-Auto Root (for Lollipop)
Do I keep my Franco kernal?
IVS IVRIS said:
Thank you for the quick reply. The rom over here: http://forum.xda-developers.com/goo...-android-4-4-3-ktu84m-rooted-busybox-t2557523 may suit my needs indeed. Although he's saying "-Don't install SuperSU (won't work, must use CF-Auto-Root)"
So, in my situation.. what I should do would be:
Factory reset
Flash rom with TWRP (my recovery)
Flash radio
Use the latest CF-Auto Root (for Lollipop)
Do I keep my Franco kernal?
Click to expand...
Click to collapse
I wouldn't use CF autoroot myself. Its similar to a toolkit which we don't recommend.
All you do is flash ROM.zip
Flash Permissive boot.img (kernel)
Flash SuperSU (It will work in this case)
I'll see if I can find a link to @sykopompos boot image
No, I don't believe franco will work. I would recommend trying ElementalX though. You flash it after the permissive boot.img. You jeep the permnissive stuff as ElementalX doesn't replace RAMdisk (just modifies it) so you get best of both worlds.
Plus ElementalX is a great kernel. You'll also be running teh same setup as me then
rootSU said:
I wouldn't use CF autoroot myself. Its similar to a toolkit which we don't recommend.
All you do is flash ROM.zip
Flash Permissive boot.img (kernel)
Flash Elemental X kernal
Flash SuperSU (It will work in this case)
I'll see if I can find a link to @sykopompos boot image
No, I don't believe franco will work. I would recommend trying ElementalX though. You flash it after the permissive boot.img. You jeep the permnissive stuff as ElementalX doesn't replace RAMdisk (just modifies it) so you get best of both worlds.
Plus ElementalX is a great kernel. You'll also be running teh same setup as me then
Click to expand...
Click to collapse
Thanks allot for the explanation! Alright, to do:
Put rom on internal memory
Boot into TWRP recovery
Whipe everything, cache, system etc.
Flash the rom
Flash the radio
Flash permissive boot.img
Flash Elemental X kernal
Flash SuperSU
Then reboot
Is that the correct way?
IVS IVRIS said:
Thanks allot for the explanation! Alright, to do:
Put rom on internal memory
Boot into TWRP recovery
Whipe everything, cache, system etc.
Flash the rom
Flash the radio
Flash permissive boot.img
Flash SuperSU
Then reboot
Is that the correct way?
Click to expand...
Click to collapse
Yep, hold on on that, let me source the link.
---------- Post added at 04:33 PM ---------- Previous post was at 04:23 PM ----------
Search the OP of this thread for "modified kernel"
http://forum.xda-developers.com/google-nexus-5/general/rom-n5-l-developer-preview-t2796003
Sorry for bothering.. I think I've got everything setup up.
I've downloaded the files:
bigxie_hammerhead_LRX21O-signed.zip (rom)
LGD820_LRX21O_RADIO.zip (radio)
N5_+LPX13D_ModifiedKernel (modified kernal)
UPDATE-SuperSU-v2.01 (SuperSU)
ElementalX-N5-2.03 (ElementalX)
Is it correct to flash it in this order? Did I get all the steps? The files I have downloaded are partially for L developer (such as SuperSU) preview.. does that matter? I also see reports of sd card not showing up.. any problems ahead?
rootSU said:
Yep, hold on on that, let me source the link.
---------- Post added at 04:33 PM ---------- Previous post was at 04:23 PM ----------
Search the OP of this thread for "modified kernel"
http://forum.xda-developers.com/google-nexus-5/general/rom-n5-l-developer-preview-t2796003
Click to expand...
Click to collapse
Sorry for bothering.. I think I've got everything setup up.
I've downloaded the files:
bigxie_hammerhead_LRX21O-signed.zip (rom)
LGD820_LRX21O_RADIO.zip (radio)
N5_+LPX13D_ModifiedKernel (modified kernal)
ElementalX-N5-2.03 (ElementalX)
UPDATE-SuperSU-v2.01 (SuperSU)
Is it correct to flash it in this order? Did I get all the steps? The files I have downloaded are partially for L developer (such as SuperSU) preview.. does that matter? I also see reports of sd card not showing up.. any problems ahead?
Guys, I got myself in some real trouble I think.
First of all:
I came from 4.4.4. stock rooted with Franco kernal
I did make a backup in TWRP, files are on my pc.
Process:
First of all, I did a factory reset in TWRP
I flashed the rom, radio, kernal for root and supersu.
First boot went fine, although WiFi couldn't be found.
I decided to boot into recovery again to wipe my SD Card
Upon rebooting, phone is looking all black without a real 'launcher', sd card not found etc.
Than:
I managed to push rom, radio, kernal and supersu to /sdcard by adb in rocovery mode
I reflashed all of these, but the same problems occur
What should I do now? I'm ****ting my pants..
IVS IVRIS said:
Guys, I got myself in some real trouble I think.
First of all:
I came from 4.4.4. stock rooted with Franco kernal
I did make a backup in TWRP, files are on my pc.
Process:
First of all, I did a factory reset in TWRP
I flashed the rom, radio, kernal for root and supersu.
First boot went fine, although WiFi couldn't be found.
I decided to boot into recovery again to wipe my SD Card
Upon rebooting, phone is looking all black without a real 'launcher', sd card not found etc.
Than:
I managed to push rom, radio, kernal and supersu to /sdcard by adb in rocovery mode
I reflashed all of these, but the same problems occur
What should I do now? I'm ****ting my pants..
Click to expand...
Click to collapse
Exactly same problem here, using the same rom. I only flashed the rom. All was fine in the first boot. The problem appeared after I formatted the sd card recovery TWRP version 2.8.0.1.. I tried also to reflash the rom with a full wipe from recovery, but nothing .. black background, no navigation bar, no sdcard and no sim is found.
Try updating TWRP to 2.8.1.0. Wipe system/data/cache/dalvik under advanced and then flash the ROM.
Sorry, only way I know how to flash a recovery is with fastboot, no zips...
Or fastboot flash the factory image but do each img separately as I hear there are still issues using the flash.all script when it comes to the system image.
jeky82 said:
Exactly same problem here, using the same rom. I only flashed the rom. All was fine in the first boot. The problem appeared after I formatted the sd card recovery TWRP version 2.8.0.1.. I tried also to reflash the rom with a full wipe from recovery, but nothing .. black background, no navigation bar, no sdcard and no sim is found.
Click to expand...
Click to collapse
Sounds exactly like me indeed. Anyone knows the steps to help us?
galakanokis said:
Try updating TWRP to 2.8.1.0. Wipe system/data/cache/dalvik under advanced and then flash the ROM.
Sorry, only way I know how to flash a recovery is with fastboot, no zips...
Or fastboot flash the factory image but do each img separately as I hear there are still issues using the flash.all script when it comes to the system image.
Click to expand...
Click to collapse
Will this fix the sd card as well?
Are people having the same problem with clockworks recovery mod?
jeky82 said:
Exactly same problem here, using the same rom. I only flashed the rom. All was fine in the first boot. The problem appeared after I formatted the sd card recovery TWRP version 2.8.0.1.. I tried also to reflash the rom with a full wipe from recovery, but nothing .. black background, no navigation bar, no sdcard and no sim is found.
Click to expand...
Click to collapse
I fixed it! Please check this post: http://forum.xda-developers.com/showpost.php?p=56743199&postcount=10 and follow the instructions.. you may have to flash the seperate .img files though, like I had to.