Related
Hi all I i eeded stock rom samsung M200s??
thank advance
samnang ouch said:
Hi all I i eeded stock rom samsung M200s??
thank advance
Click to expand...
Click to collapse
these are the factory images. be sure you get the one for m200....there are several devices on this page.
https://developers.google.com/android/nexus/images
Thank for reply but i need M200s not M200 .
Please Help
I Have a Korean Version of Nexus S (m200) flashed w/ custom Rom 4.2 Hellybean,
can someone help me Flash the Official Stock Rom 4.1 JellyBean please?
and another thing, if it is flashed does my phone still openline (all sim available)?
samnang ouch said:
Thank for reply but i need M200s not M200 .
Click to expand...
Click to collapse
No such thing exists. It's m200.
summereyes said:
I Have a Korean Version of Nexus S (m200) flashed w/ custom Rom 4.2 Hellybean,
can someone help me Flash the Official Stock Rom 4.1 JellyBean please?
and another thing, if it is flashed does my phone still openline (all sim available)?
Click to expand...
Click to collapse
Get that. And read the instructions.
hp420 said:
these are the factory images. be sure you get the one for m200....there are several devices on this page.
https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
Get that. And read the instructions.[/QUOTE]
i already downloaded the factory image for my phone but, i dont know how to flash it please give some step by step procedure please
summereyes said:
Get that. And read the instructions.
Click to expand...
Click to collapse
i already downloaded the factory image for my phone but, i dont know how to flash it please give some step by step procedure please[/QUOTE]
You will find these files useful if you have used the Android Open-Source Project, flashed custom builds on your device, and wish to return that device to its factory state.
In order to use these files, you need to have the fastboot tool in your PATH. That tool is compiled as part of every configuration of the Android Open-Source Project and is the tool used to flash custom builds on your device. On GNU/Linux systems, this also implies that you have configured USB access as mentioned in the machine setup instructions.
Your device needs to be in fastboot mode, with the bootloader unlocked. The relevant key combinations and commands are documented on the page about building for devices.
You need to uncompress each download before use, which creates a new directory for that exact download. That directory contains a ./flash-all.sh script, which handles the various operations, installs the necessary bootloader, baseband firmware(s), and operating system. Note that this operation deletes all user data by default.
After restoring a factory image, it is recommended that you lock the bootloader, for security reasons.
Click to expand...
Click to collapse
So, more or less
Have fastboot working
Boot in fastboot mode
Make sure you untar every file from the link above.
wipe data
fastboot -w update image-sojuk-JRO03E.zip
Hi guys,
I'm a total noob regarding ROMs, root, etc..
My Infinity is getting really laggy, and I really need to bring it to a new life..
I was looking for an ideal CMInstaller situation like i used on my Galaxy Note N7000.. This little app is great cuz it does everything for us and noob users like myself don't need to be afraid to brick their devices..
Is there any really easy solution like this so I can safely flash my TF700?
TIA.
I think the answer is yes and no
I run CROMI-X on this tablet, but recently I download the latest CM and the link provided kept bouncing me to the Playstore to dl an installer app. I prefer to use my recovery, so I did not use it. But that's probably what you are looking for.
The thing is, on this device first you need to unlock the bootloader and push a custom recovery to it before you can even use an installer app. You also need to make sure that you have the correct bootloader installed before you flash the CM rom.
Check out the CM thread in the Development section.
CMInstaller so far is only compatible to most common Galaxy and nexus devices, and htc one.
http://wiki.cyanogenmod.org/w/CyanogenMod_Installer#Supported_Devices
I am honestly afraid to flash my device without assistance because there are so many things to do and none of it seems easy.. I'm bootloader unlocked running stock 4.1.2, and the steps needed to take scare me..
1 - update to stock 4.2.1 (according to what I've read..)
2 - Root
3 - NVFlash
4 - Custom recovery
5 - Custom ROM
I don't even know if these steps are in proper order, but seems that so many things could go wrong.. Could you help me doing this easily and problem free? I need to do something to take full advantage of my TF700.. It clearly isn't working properly on stock.
Thanks.
madz78 said:
CMInstaller so far is only compatible to most common Galaxy and nexus devices, and htc one.
http://wiki.cyanogenmod.org/w/CyanogenMod_Installer#Supported_Devices
I am honestly afraid to flash my device without assistance because there are so many things to do and none of it seems easy.. I'm bootloader unlocked running stock 4.1.2, and the steps needed to take scare me..
1 - update to stock 4.2.1 (according to what I've read..)
2 - Root
3 - NVFlash
4 - Custom recovery
5 - Custom ROM
I don't even know if these steps are in proper order, but seems that so many things could go wrong.. Could you help me doing this easily and problem free? I need to do something to take full advantage of my TF700.. It clearly isn't working properly on stock.
Thanks.
Click to expand...
Click to collapse
I recently wrote a tutorial on Android Central for people who are new to flashing. Check it out and if anything is left unclear - ask
http://forums.androidcentral.com/as...6920-tutorial-flashing-custom-rom-tf700t.html
Hi, I read the tutorial and I already have some questions even before i start..
- Can't my device be rooted? I believe I need root for apps to access superuser, and for performance menu (or overclock).
- Where's NVFlash? If NVFlash avoids bricking my device I believe this is a MUST have if I intend to grow and experiment different recoveries, kernels and ROMs.
- My device FW ver. is 10.4.4.18, do I need to update to 10.6.1.14.10 in order to continue, or can i do it from 10.4.4.18 and still take advantage of the loophole Motochopper exploited to gain root on this device?
Thanks.
madz78 said:
Hi, I read the tutorial and I already have some questions even before i start..
- Can't my device be rooted? I believe I need root for apps to access superuser, and for performance menu (or overclock).
- Where's NVFlash? If NVFlash avoids bricking my device I believe this is a MUST have if I intend to grow and experiment different recoveries, kernels and ROMs.
- My device FW ver. is 10.4.4.18, do I need to update to 10.6.1.14.10 in order to continue, or can i do it from 10.4.4.18 and still take advantage of the loophole Motochopper exploited to gain root on this device?
Thanks.
Click to expand...
Click to collapse
You don't need to be rooted to flash a custom ROM. You can root from 14.8 as you don't need to go to 14.10. If you are on 10.4.4.18 you are on a really old boot loader for 4.1 and will need to upgrade if you want to unlock and flash the latest ROMs.
madz78 said:
Hi, I read the tutorial and I already have some questions even before i start..
- Can't my device be rooted? I believe I need root for apps to access superuser, and for performance menu (or overclock).
- Where's NVFlash? If NVFlash avoids bricking my device I believe this is a MUST have if I intend to grow and experiment different recoveries, kernels and ROMs.
- My device FW ver. is 10.4.4.18, do I need to update to 10.6.1.14.10 in order to continue, or can i do it from 10.4.4.18 and still take advantage of the loophole Motochopper exploited to gain root on this device?
Thanks.
Click to expand...
Click to collapse
Jeez - where did you dig up this version? I believe that was one of the first JB versions? Yes, Motochopper should work, but: Why root if you can't use Goo Manager to get a custom recovery installed? If that is your goal....
Yes, you can just root the stock ROM, but it does not give you that many options to improve the performance of this tablet. And any custom rom is rooted - so why bother?
To have NVflash is great and a wonderful reassurance and I do flash with greater abandon since I got them, but generating the blobs was the most stressful procedure in my limited flashing experience.
I don't know how comfortable you are with using cmd and fastboot - but I sure was glad to have some experience with flashing recoveries and such before I started it!
Generating the NVflash blobs involves flashing a bootloader and recovery build just for that procedure, so you need to know how to flash those in the first place (and how to flash back to your daily driver recovery/bootloader afterrwards).
There's nowhere for you to go without a custom recovery. Start with that.
I have no idea if the recovery most of us use (TWRP 2.6.1 or 2.6.3.1 - both are fine) works with the BL you currently have.
So I would update to the latest firmware, fastboot TWRP and then install CROMi-X.
You can dive into getting your NVflash blobs as soon as you have TWRP installed - that's up to you.
Edit: sbdags was faster - as usual
So there you have it: You have to update your stock firmware before you install TWRP
Wow guys.. This is why i never flash anything since bada on my Wave..
It's all so technical, confusing and intimidating.. God!!
Ok. I really need to start understanding this, so, if I got it right, I don't need to root because the custom ROM is already rooted.. Good!
Now the hard part. Please be patient and gentle, explain me like I'm 5 yo child.
- If I understood correctly first thing is upgrade FW, but to which FW should i upgrade? 10.6.1.14.10 or 10.6.1.14.8? If custom ROM is rooted, does the FW matter or not?
- Next comes recovery. Again, which one should I choose? (sdbags your opinion would be really important for me here, considering CROMi-X 5.2.2 is developed by you and the ROM i chose)
- I think I'll leave any ROM questions for later, after i finally understand these first 2 steps.
Also, regarding NVFlash, what the bleep is blobs? I'm comfortable with cmd but never used fastboot.
Thanks again!
madz78 said:
Wow guys.. This is why i never flash anything since bada on my Wave..
It's all so technical, confusing and intimidating.. God!!
Click to expand...
Click to collapse
Naaah - if I understood it, it can't be technical Just take your time, read - Google is your friend.
Ok. I really need to start understanding this, so, if I got it right, I don't need to root because the custom ROM is already rooted.. Good!
Click to expand...
Click to collapse
See? You got that right already.
Now the hard part. Please be patient and gentle, explain me like I'm 5 yo child.
- If I understood correctly first thing is upgrade FW, but to which FW should i upgrade? 10.6.1.14.10 or 10.6.1.14.8? If custom ROM is rooted, does the FW matter or not?
Click to expand...
Click to collapse
It does not matter. As long as you upgrade to a 10.6.1.x version, your bootloader will be compatible with TWRP 2.6.1 or 2.6.3.1 - see below.
- Next comes recovery. Again, which one should I choose? (sdbags your opinion would be really important for me here, considering CROMi-X 5.2.2 is developed by you and the ROM i chose)
- I think I'll leave any ROM questions for later, after i finally understand these first 2 steps.
Click to expand...
Click to collapse
sbdags is currently recommending TWRP 2.6.1. That is the version he included in the bootloader/TWRP package he provides in the OP (Original Post) of the CROMi-X thread.
To elaborate: In flashing custom roms the most important aspect is that you always have a compatible bootloader/recovery combination. You use your recovery to flash roms, bootloaders, kernels, wipe all or part of your SD card - the works.
If your recovery gets corrupted but you can still boot into the bootloader, you can install a new recovery using the fastboot protocol (which provides low level access from your computer). If your bootloader gets corrupted (and the most common cause is the wrong recovery) and you cannot boot into recovery, NVflash is your last chance to recover the tablet because: no bootloader = no fastboot access.
The easiest way to get a current bootloader in your situation would be to upgrade your stock firmware. The risk for something to go wrong is close to negative 1
Then you would download TWRP 2.6.1 for the TF700 from the Teamwin website and use the fastboot protocol to install it to it's proper partition.
Risk level is very low if you can follow the instructions in my little tutorial or in the Minimal ADB Fastboot Tool thread.
Once you have TWRP installed (and you tested that it's working) you could - and this is totally optional - flash the bootloader/TWRP package from sbdags OP. Just to make 100% sure you are on the correct combo.....
Also, regarding NVFlash, what the bleep is blobs? I'm comfortable with cmd but never used fast boot.
Thanks again!
Click to expand...
Click to collapse
A blob is a file - better: an image. Binary Large Object is the origin, I believe. For a technical explanation don't ask me! Go here:
http://en.m.wikipedia.org/wiki/Binary_large_object
If you look into the Asus firmware zip file, inside is a blob and a meta data file (if memory serves me right). The blob is the system image.
What if while you are flashing a firmware and your power supply is reaching 0%, could it be a high risk? :silly:
LetMeKnow said:
What if while you are flashing a firmware and your power supply is reaching 0%, could it be a high risk? :silly:
Click to expand...
Click to collapse
Damn you! I was trying to reassure this chap! LOL
There's no remedy for stupidity - so as a scientist you just ignore what you can't account for, right?
berndblb said:
Damn you! I was trying to reassure this chap! LOL
There's no remedy for stupidity - so as a scientist you just ignore what you can't account for, right?
Click to expand...
Click to collapse
Just asked a question and thanks for helping... Hahaha:laugh:
LetMeKnow said:
Just asked a question and thanks for helping... Hahaha:laugh:
Click to expand...
Click to collapse
Yes, a just a little, totally correct but diabolical question.....
Didn't know you had that evil streak in you, friend
berndblb said:
Yes, a just a little, totally correct but diabolical question.....
Didn't know you had that evil streak in you, friend
Click to expand...
Click to collapse
I am trying to relax from a long day of work and tiring of tweaking my device... I am looking for someone to talk to.. Maybe, I need to give up my device and back to my normal boring life...
berndblb said:
Naaah - if I understood it, it can't be technical Just take your time, read - Google is your friend.
See? You got that right already.
It does not matter. As long as you upgrade to a 10.6.1.x version, your bootloader will be compatible with TWRP 2.6.1 or 2.6.3.1 - see below.
sbdags is currently recommending TWRP 2.6.1. That is the version he included in the bootloader/TWRP package he provides in the OP (Original Post) of the CROMi-X thread.
To elaborate: In flashing custom roms the most important aspect is that you always have a compatible bootloader/recovery combination. You use your recovery to flash roms, bootloaders, kernels, wipe all or part of your SD card - the works.
If your recovery gets corrupted but you can still boot into the bootloader, you can install a new recovery using the fastboot protocol (which provides low level access from your computer). If your bootloader gets corrupted (and the most common cause is the wrong recovery) and you cannot boot into recovery, NVflash is your last chance to recover the tablet because: no bootloader = no fastboot access.
The easiest way to get a current bootloader in your situation would be to upgrade your stock firmware. The risk for something to go wrong is close to negative 1
Then you would download TWRP 2.6.1 for the TF700 from the Teamwin website and use the fastboot protocol to install it to it's proper partition.
Risk level is very low if you can follow the instructions in my little tutorial or in the Minimal ADB Fastboot Tool thread.
Once you have TWRP installed (and you tested that it's working) you could - and this is totally optional - flash the bootloader/TWRP package from sbdags OP. Just to make 100% sure you are on the correct combo.....
A blob is a file - better: an image. Binary Large Object is the origin, I believe. For a technical explanation don't ask me! Go here:
http://en.m.wikipedia.org/wiki/Binary_large_object
If you look into the Asus firmware zip file, inside is a blob and a meta data file (if memory serves me right). The blob is the system image.
Click to expand...
Click to collapse
The Asus blob actually contains the system image, kernel, recovery, bootloader and partition table.
I have HTC One x (At&T) US Version and using it in India.
It has Stock ICS 4.0.4 and Already Rooted,
Already S-OFF,
has Custom Recovery TWRP and
SCID is 111111111 and
Software number/Build Number is 2.20 and
Kernel version is 3.0.8-01558 .....
Now my Questions is :
1. How to Update is to jelly Bean and if i Update it to Stock/Custom jelly bean then do i have to unlock/S-off it again? If Yes then How to do it? Any Given Link will be Highly Appreciated.
2. I read some Posts/Comments on some 4.2.2 Custom roms threads that "Highly recommend latest Jellybean firmware".. what does that mean? (my confusion is if i already have latest jelly Bean Firmware then why would i search update for jelly bean? )
3. if it is recommended to have latest jelly bean firmware before update to 4.2.2 then can anybody give me the link for that?
4. HTC One x AT&T has beats Audio.. if i update it to Any 4.2.2 Custom Rom.. then will beats Audio Work on new Rom? (I know it is Noob Question but i really want to know because i want Beats Audio For Music)
Thanks in Advance
1. All you need to do is install a stock 4.1 ROM from our Android Development section. Or you can install a custom ROM if you want to. The How-To Guide For Beginners link in my signature details how to do this, along with other basic operations.
2. The reason there are recommendations to flash the 2.15 firmware is because many people with a modified phone don't have the latest firmware even though they might have the latest ROM. In the world of modified phones it's completely normal to switch ROMs without changing your firmware. For someone with an unmodified phone the only way to upgrade your ROM is to also upgrade your firmware. Before deciding if you need to do this (you most likely do) I need your bootloader details, the first five lines.
3. You'll find the firmware package along with install instructions in the first post of this thread.
4. Yes, Beats is incorporated into all current Sense ROMs. If you decide to install an aosp ROM it isn't incorporated.
Further to all those answers, I'd strongly recommend you do a lot of reading before proceeding with anything. Modifying a phone requires a certain level of knowledge, without knowing what you're doing (and the consequences) you can quickly get in over your head and end up with a device that won't boot, or worse.
Click the Everything Evita link in my signature, it's a resource thread that contains links to everything you'll need, make sure you bookmark that thread. Click the other links in my signature too, you'll find a wealth of very useful information in those threads. I'd also suggest you browse our forum for a few days to get a firm grasp on things. I'll put it like this, I researched for two weeks before modifying my phone.
Sent from my Evita
timmaaa said:
1. All you need to do is install a stock 4.1 ROM from our Android Development section. Or you can install a custom ROM if you want to. The How-To Guide For Beginners link in my signature details how to do this, along with other basic operations.
2. The reason there are recommendations to flash the 2.15 firmware is because many people with a modified phone don't have the latest firmware even though they might have the latest ROM. In the world of modified phones it's completely normal to switch ROMs without changing your firmware. For someone with an unmodified phone the only way to upgrade your ROM is to also upgrade your firmware. Before deciding if you need to do this (you most likely do) I need your bootloader details, the first five lines.
3. You'll find the firmware package along with install instructions in the first post of this thread.
4. Yes, Beats is incorporated into all current Sense ROMs. If you decide to install an aosp ROM it isn't incorporated.
Further to all those answers, I'd strongly recommend you do a lot of reading before proceeding with anything. Modifying a phone requires a certain level of knowledge, without knowing what you're doing (and the consequences) you can quickly get in over your head and end up with a device that won't boot, or worse.
Click the Everything Evita link in my signature, it's a resource thread that contains links to everything you'll need, make sure you bookmark that thread. Click the other links in my signature too, you'll find a wealth of very useful information in those threads. I'd also suggest you browse our forum for a few days to get a firm grasp on things. I'll put it like this, I researched for two weeks before modifying my phone.
Sent from my Evita
Click to expand...
Click to collapse
First of all thanks a lot for replying So fast and giving your time to help me...
my bootloder details:
*** TAMPERED ***
*** UNLOCKED ***
EVITA PVT SHIP S-OFF RL
CID- 11111111
HBOOT-1.14.0002
and also my Software number/Build Number is 2.20 and
Kernel version is 3.0.8-01558 ..... is it ok or first i need to update both ?
If you want to update to Android 4.2.2 and Sense 5 you first need to flash the 2.15 firmware found in the thread I linked you to before. Do you have a custom recovery installed? If so all you need to do after flashing the firmware is to install a ROM of your choosing. If not, just look in my How-To thread for instructions on how to do that. There's no need to worry about your current ROM/kernel, flashing a ROM will update those.
Sent from my Evita
timmaaa said:
If you want to update to Android 4.2.2 and Sense 5 you first need to flash the 2.15 firmware found in the thread I linked you to before. Do you have a custom recovery installed? If so all you need to do after flashing the firmware is to install a ROM of your choosing. If not, just look in my How-To thread for instructions on how to do that. There's no need to worry about your current ROM/kernel, flashing a ROM will update those.
Sent from my Evita
Click to expand...
Click to collapse
i have build number 2.20.502.7.. do i still need 2.15 firmware?
For the third time, yes. Your build number is irrelevant anyway.
Sent from my Evita
timmaaa said:
For the third time, yes. Your build number is irrelevant anyway.
Sent from my Evita
Click to expand...
Click to collapse
i am stuck at firmware...this error comes everytime... screenshot attached... please see ...
Try opening the command prompt from within the fastboot folder. To do this just navigate to the location on your PC where fastboot.exe is located, then shift + right click anywhere within that folder, then select open command prompt here. Now start the process from the beginning. Then when you get to the part where you flash the firmware you don't need to cd to the location, you just do this:
Code:
fastboot flash zip firmware.zip
Sent from my Evita
timmaaa said:
Try opening the command prompt from within the fastboot folder. To do this just navigate to the location on your PC where fastboot.exe is located, then shift + right click anywhere within that folder, then select open command prompt here. Now start the process from the beginning. Then when you get to the part where you flash the firmware you don't need to cd to the location, you just do this:
Code:
fastboot flash zip firmware.zip
Sent from my Evita
Click to expand...
Click to collapse
everything has done successfully... thanks a lot for you help...
but
when i rebooted my phone (ICS) and gone to Settings>about>Software Information... it still showing 2.20.502.7 710RD.... is it normal or something is wrong..... Attached Screenshots both.. phone and my command window.... please check this.. (i am sorry i am disturbing u
a lot coz i am noob :'( )
You still have the 2.20 build number because that's the ROM version that is currently installed on your device. All you have done so far is update your firmware, that's completely separate to your ROM.
At this point all you need to do now is install a ROM. You'll find Sense 5 ROMs in our Android Development. You'll find instructions on installing a ROM in my How-To Guide For Beginners thread in my signature.
To install a ROM you first need a custom recovery, go into your bootloader and select recovery, tell me what happens.
Sent from my Evita
timmaaa said:
You still have the 2.20 build number because that's the ROM version that is currently installed on your device. All you have done so far is update your firmware, that's completely separate to your ROM.
At this point all you need to do now is install a ROM. You'll find Sense 5 ROMs in our Android Development. You'll find instructions on installing a ROM in my How-To Guide For Beginners thread in my signature.
To install a ROM you first need a custom recovery, go into your bootloader and select recovery, tell me what happens.
Sent from my Evita
Click to expand...
Click to collapse
Yes, i have already installed Custom Recovery TWRP... now i think all i need to do is install a ROM .... so should i directly install any 4.2.2 custom ROM or first i should install 4.1 then after 4.2 ?
You can install any custom ROM you like, no need to install a 4.1 ROM first. But you should make a backup, check my How-To Guide For Beginners thread for instructions on how to do that.
Sent from my Evita
timmaaa said:
You can install any custom ROM you like, no need to install a 4.1 ROM first. But you should make a backup, check my How-To Guide For Beginners thread for instructions on how to do that.
Sent from my Evita
Click to expand...
Click to collapse
Oh!! yehhh .. nice nice nice... thanks a lot a lot a lot......u r really nice person... u made my Day...
No problems, glad I could help.
Sent from my Evita
timmaaa said:
No problems, glad I could help.
Sent from my Evita
Click to expand...
Click to collapse
last Questions .. hope u dont mind...
1. if i install Any "STOCK" Rom then do i have to S-OFF/Unlock/Super CID Again?
2: I chose this ROM http://forum.xda-developers.com/showthread.php?t=1655011
But it says it is with At&T settings ... my confusion is , my phone is US version.. and i am using it in India.. AT&T is not in india... so if i install this rom then will my sim work after installing this ROm....
and i downloaded this Rom and tried to flash in TWRP recovery.. but it is failing everytime.. and i did factory reset (wipe data, cache and dalvik .android_secure)... now i am unable to use my old rom...what should i do now?
info2shail2010 said:
last Questions .. hope u dont mind...
1. if i install Any "STOCK" Rom then do i have to S-OFF/Unlock/Super CID Again?
2: I chose this ROM http://forum.xda-developers.com/showthread.php?t=1655011
But it says it is with At&T settings ... my confusion is , my phone is US version.. and i am using it in India.. AT&T is not in india... so if i install this rom then will my sim work after installing this ROm....
Click to expand...
Click to collapse
Installing a stock ROM doesn't affect your bootloader or your s-on/s-off status, it only writes to the /system partition.
That ROM does contain some at&t elements, but whatever SIM card you're currently using should be perfectly fine. Once you've SIM unlocked a device you can use any SIM card on it.
Basically you can use any ROM found within our device forum and you'll be ok.
Sent from my Evita
timmaaa said:
Installing a stock ROM doesn't affect your bootloader or your s-on/s-off status, it only writes to the /system partition.
That ROM does contain some at&t elements, but whatever SIM card you're currently using should be perfectly fine. Once you've SIM unlocked a device you can use any SIM card on it.
Basically you can use any ROM found within our device forum and you'll be ok.
Sent from my Evita
Click to expand...
Click to collapse
i downloaded this Rom and tried to flash in TWRP recovery.. but it is failing everytime.. and i did factory reset (wipe data, cache and dalvik .android_secure)... now i am unable to use my old rom...what should i do now?
Exactly which version of TWRP have you installed? Did you make a backup earlier like I suggested? If so you can use the restore feature in TWRP to restore that backup of your previous ROM. I do need to know which TWRP version you're using though.
Sent from my Evita
---------- Post added at 01:58 AM ---------- Previous post was at 01:57 AM ----------
Also, did you check the md5 of the ROM after downloading it?
Sent from my Evita
timmaaa said:
Exactly which version of TWRP have you installed? Did you make a backup earlier like I suggested? If so you can use the restore feature in TWRP to restore that backup of your previous ROM. I do need to know which TWRP version you're using though.
Sent from my Evita
---------- Post added at 01:58 AM ---------- Previous post was at 01:57 AM ----------
Also, did you check the md5 of the ROM after downloading it?
Sent from my Evita
Click to expand...
Click to collapse
TWRP : 2.5
Back Up : No ( i thaught back up is for my personal data.. that i already have in ma pc )
MD5.. i didnt get it... what is md5, where to find and what to check in it and how to check ?
info2shail2010 said:
TWRP : 2.5
Back Up : No ( i thaught back up is for my personal data.. that i already have in ma pc )
MD5.. i didnt get it... what is md5 and what to check in it ?
Click to expand...
Click to collapse
Ok there's your problem, TWRP 2.5 is full of bugs. Download the modified version of TWRP 2.6*from here. Put the file in your fastboot folder. Connect phone in fastboot mode, open command prompt from within fastboot folder, issue the following commands:
Code:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Now you should be able to install the ROM.
An md5 is like a digital fingerprint of a file. It will be listed on the download page for a ROM/kernel/radio. What you do is use an md5 checking app/program to check that the md5 of the downloaded file matches the md5 listed on the download page. If it matches you're all good, if it doesn't match it means the file became corrupted during the download. You should always check the md5 of anything you're about to flash, a corrupt file could damage your phone if you install it.
Once you have installed the ROM you should reboot back into TWRP and use the backup feature to backup system/data/boot. Then if you have any problems in the future you can use the restore feature to restore it and you'll have a working OS.
It's also a good way to have your favourite ROMs backed up. Once I decide I like a ROM I set it up with all my apps and settings and then make a backup. That way if I ever want to use that ROM in future I can easily restore the backup and have a fully setup ROM ready to go. It's much easier than installing a ROM from scratch and setting it up all over again.
Sent from my Evita
hi !
few month ago i rooted my nexus5 and installed a custom rom (pure nexus), everything was OK. but today i tried to install the last version of "pure nexus", so i downloaded the zip file, pushed it on the device, launched a flash zip with nexus root toolkit (everything was ok on the screen) but then it restart, and get stuck during the boot (4 small circle rotating...)
maybe i've done something wrong? how can i fix it?
(sorry i'm a noob !)
thanks!
nel0 said:
hi !
few month ago i rooted my nexus5 and installed a custom rom (pure nexus), everything was OK. but today i tried to install the last version of "pure nexus", so i downloaded the zip file, pushed it on the device, launched a flash zip with nexus root toolkit (everything was ok on the screen) but then it restart, and get stuck during the boot (4 small circle rotating...)
maybe i've done something wrong? how can i fix it?
(sorry i'm a noob !)
thanks!
Click to expand...
Click to collapse
Hi!
Congratulations, this is your first bootloop. Nothing to worry about. I guess your problem is due to the fact that you were coming from a lollipop based custom rom. Before you install a marshmallow based custom rom you need to install the marshmallow factory image first. If you're using the nexus root toolkit you can always click on the magic "flash stock - unroot" button. This is the easiest way for you.
My suggestion is to flash the factory image manually with ADB. In this way you'll know the basics of modding and it will be very useful for you in future. If you want you can follow this guide http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
vorinc said:
Hi!
Congratulations, this is your first bootloop. Nothing to worry about. I guess your problem is due to the fact that you were coming from a lollipop based custom rom. Before you install a marshmallow based custom rom you need to install the marshmallow factory image first. If you're using the nexus root toolkit you can always click on the magic "flash stock - unroot" button. This is the easiest way for you.
My suggestion is to flash the factory image manually with ADB. In this way you'll know the basics of modding and it will be very useful for you in future. If you want you can follow this guide http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
Click to expand...
Click to collapse
thanks for your answer!
alright, after installing a marshmallow factory image, everything was OK \0/
so i was wondering : is it possible to "update" a custom rom without wiping everything? :/ (is that what people call a dirty flash?)
thanks again for your help
nel0 said:
is it possible to "update" a custom rom without wiping everything? :/ (is that what people call a dirty flash?)
Click to expand...
Click to collapse
Yes, that's what "dirty flash" means. It is possible as long as the update doesn't concern an android version. An example is your case: lollipop-->marshmallow.
In facts custom roms (differently from factory images) do not provide boot.img in their zips; they assume you already have installed in your device. The lack of the correct boot.img caused your bootloop
vorinc said:
Yes, that's what "dirty flash" means. It is possible as long as the update doesn't concern an android version. An example is your case: lollipop-->marshmallow.
In facts custom roms (differently from factory images) do not provide boot.img in their zips; they assume you already have installed in your device. The lack of the correct boot.img caused your bootloop
Click to expand...
Click to collapse
oh, ok, understood. Thanks for the precision !
Hello, I'm a noob at this so please be kind. I followed the below:
http://forum.xda-developers.com/tra...inners-guide-unlock-custom-rom-tf300-t3061648
I successfully:
Unlocked my TF300T's Bootloader
Installed custom recovery using fastboot
Rooted my tablet
Debloated the Tablet (Titanium Backup)
Backup up my current (OEM) SYSTEM ROM to microSD
So now I'm onto attempting a custom ROM. I'm a bit bored with 4.2.1 and would like to go to the same version of ROM my Note 7 has which is 6.0.1 Marshmallow or even try the new 7.0 Nougat.
I'm a little confused as to what ROM will or will not work. I see a few ROMS worth trying, but there install instructions reference a different Bootloader multiple flashes such as SuperSU or gapps.
Whats the best fool proof method to flash a new ROM with what I have and are there any simple one file ROM/ZIP/ Blob etc.. file that would do what I want?
Thank you.
broderp said:
Hello, I'm a noob at this so please be kind. I followed the below:
http://forum.xda-developers.com/tra...inners-guide-unlock-custom-rom-tf300-t3061648
I successfully:
Unlocked my TF300T's Bootloader
Installed custom recovery using fastboot
Rooted my tablet
Debloated the Tablet (Titanium Backup)
Backup up my current (OEM) SYSTEM ROM to microSD
So now I'm onto attempting a custom ROM. I'm a bit bored with 4.2.1 and would like to go to the same version of ROM my Note 7 has which is 6.0.1 Marshmallow or even try the new 7.0 Nougat.
I'm a little confused as to what ROM will or will not work. I see a few ROMS worth trying, but there install instructions reference a different Bootloader multiple flashes such as SuperSU or gapps.
Whats the best fool proof method to flash a new ROM with what I have and are there any simple one file ROM/ZIP/ Blob etc.. file that would do what I want?
Thank you.
Click to expand...
Click to collapse
Congratulations! Everything you did looks fine. So you are ready to install a custom rom. I would like to suggest one of the best: http://forum.xda-developers.com/transformer-tf300t/development/rom-t3453702 (You may follow up the tread and report there!)
Please take care very exactly on the installation instruction in post #1 given by Timduru. And don't forget that you need Kang TWRP [email protected] Download here: http://forum.xda-developers.com/transformer-tf300t/development/recovery-twrp-t3046479. That's mandatory!
Good luck!
ebonit said:
Congratulations! Everything you did looks fine. So you are ready to install a custom rom. I would like to suggest one of the best: http://forum.xda-developers.com/transformer-tf300t/development/rom-t3453702 (You may follow up the tread and report there!)
Please take care very exactly on the installation instruction in post #1 given by Timduru. And don't forget that you need Kang TWRP [email protected] Download here: http://forum.xda-developers.com/transformer-tf300t/development/recovery-twrp-t3046479. That's mandatory!
Good luck!
Click to expand...
Click to collapse
Thanks. As simple as the process was, as a noob (first time attempting this) I was really concerned about screwing this up and bricking my tablet.
The one you linked to was one of the ones I was considering and hence my question regarding what works with what I have already done. The noob mind (mine anyways) finds a dozen questions at every turn. In this case I would ask the following:
Q-Do I have to use Kang TWRP?
Q-How is it different than the TWRP I used on my Tablet?
Q-Will I need to constantly change TWRP versions depending on what ROM I want to use?
Q-Is there a danger to switching TWRPs?
Q-Doesn't flashing SuperSU after I flash Gapps overright and erase SuperSU or is there some unique way to flash (push?) both at the same time?
Q-Many more I'm sure!
To the noob, almost all the instructions I read appear to be written for someone who as done this many times. The level of detail needed for the novice is just not there or lost between the jargon used, with many steps not fleshed out because the author assumes a certain level of expertise.
I will definitely read these threads as best I can, but in the interim, is there any ROM that are known to be able to be flashed via the TWRP I currently have? The author of the version I used certainly made it seem like it was that simple, load the ROM/ zip file onto the MicroSD card and when in Custom recovery simply use the INSTALL feature to navigate to the file and press a button to flash and ..."BAM!!" you are running a new ROM.
ebonit said:
...
Please take care very exactly on the installation instruction in post #1 given by Timduru. And don't forget that you need Kang TWRP [email protected] Download here: http://forum.xda-developers.com/transformer-tf300t/development/recovery-twrp-t3046479. That's mandatory!
Good luck!
Click to expand...
Click to collapse
That version of KANG appears to be dead, as the thread has been closed and abondoned by the OP. So no new questions or help there....
Can I install that version over the top of my current version of TWRP the same way I did the first time? (change file to TWRP.blob etc.)
broderp said:
That version of KANG appears to be dead, as the thread has been closed and abondoned by the OP. So no new questions or help there....
Can I install that version over the top of my current version of TWRP the same way I did the first time? (change file to TWRP.blob etc.)
Click to expand...
Click to collapse
Please don't brick your tablet. First download Kang TWRP. It isn't dead. Try this https://www.androidfilehost.com/?fid=24052804347781183.
broderp said:
Can I install that version over the top of my current version of TWRP the same way I did the first time? (change file to TWRP.blob etc.)
Click to expand...
Click to collapse
Yes you can.
However Kang TWRP is a xxx.img file. You also can use your current TWRP and flash the image file. Attached you will find an image and a zip version.
ebonit said:
Please don't brick your tablet. First download Kang TWRP. It isn't dead. Try this https://www.androidfilehost.com/?fid=24052804347781183.
Click to expand...
Click to collapse
Sorry, bad choice of words on my part. By dead I meant that the thread was closed and I'm concerned getting answers would be harder as the OP was no longer actively looking there for questions.
ebonit said:
Yes you can.
However Kang TWRP is a xxx.img file. You also can use your current TWRP and flash the image file. Attached you will find an image and a zip version.
Click to expand...
Click to collapse
Ok, so if I read your comment correctly, I can copy the .img file to an SD card, boot into recovery and flash it from there OR I can fire up fastboot and the same steps I originally did to install custom recovery from my PC to accomplish the same thing... either way I should still have custom recovery, but with the KANG version. Right?
THANKS TO BOTH OF YOU FOR RESPONDING TO MY PREVIOUS POST. I appreciate the support.
Oh no....
Well crap. I put the .img file on my SD card and boot the tablet into recovery, I flashed the .img file to the rovery not boot partition. All appeared well....but when I go back to see if I have KANG recovery, it hangs anbd says Booting Failure Unrecoverable bootloader error (0x000000000)
EDIT: After I cleaned my pants, I used abd and fastboot to flash the original Blob file using my PC. This restored the custom recovery. I was freaking out for a few minutes.
I didn't change the file name of the kang .img file. Should I have done something different?
EDIT: Successful recovery to Kang2.8.7.2 !! :good::good: I used adb and my PC to send the .img file (renamed "twrpkang.img" for simplicity) and it worked great. I'm a pro..:silly:
broderp said:
Well crap. I put the .img file on my SD card and boot the tablet into recovery, I flashed the .img file to the rovery not boot partition. All appeared well....but when I go back to see if I have KANG recovery, it hangs anbd says Booting Failure Unrecoverable bootloader error (0x000000000)
Click to expand...
Click to collapse
Bad luck! Could you please describe what does it mean? : "I flashed the .img file to the rovery not boot partition."
ebonit said:
Bad luck! Could you please describe what does it mean? : "I flashed the .img file to the rovery not boot partition."
Click to expand...
Click to collapse
Not sure what I did wrong. I tried to do it within the old recovery menu and it hosed it. It found the file and mounted it successfully, but it seemed weird to be within the partition I was overwriting and writing to it. Kind of like you cant install windows while your using Windows...
The new version is much smoother.... Thanks, not to learn about this gapps super SU and how to flash all of these and in what order along with the ROM..as well as this wipe vs format thing...so confusing...