Related
NEXUS 7 3G-"nakasig" - Jelly Bean/KitKat Discussions, Problems and Solutions
Hi Nexus 7 "Nakasig" users,
I would like to consider this thread as your one place to chat or anything else related to Jelly Bean on the NEXUS 7 - 3G
I need everyone help to keep this thread somewhat sane, report any trolling or flaming and don't respond to it.
Keep all your posts in this thread polite and make sure you follow The Forum Rules.
I request you to stop posting:
- 'Thanks this helped'
- 'Yeah Me too'
-'+1'
These kind of posts are useless instead use the thanks button to show your appreciation
Click to expand...
Click to collapse
For all your JB needs, go to:
==>[Index] All for NEXUS 7 - "Nakasig" - (GSM/HSPA+)
==>[GUIDE] Unlock and Root a Nexus 7 3G “Nakasig- Tilapia”
==> [GUIDE][BOOTLOADER][4.3] TILAPIA JWR66V - 4.23 Flash Image Instructions - UPDATE
==>[GUIDE]If you need some help for install SDK and ADB drivers in Win 7, you can use this guide which is really good and comprehensive for all of us
It will be better for you to find one thread where we can concentrate all discussions, problems and solutions for the Nexus 7 3G
It 's a tool which is very good if you want to buy a Google Nexus Devices :good:
Google Nexus Devices World Availability Checker
Top man!
Any one got a working recovery and supersu/superuser that works with 4.2?
Since I've heard people losing 3G and stuff when they rooted, and I kinda don't want to have to set my stuff up again
WarningHPB said:
Top man!
Any one got a working recovery and supersu/superuser that works with 4.2?
Since I've heard people losing 3G and stuff when they rooted, and I kinda don't want to have to set my stuff up again
Click to expand...
Click to collapse
You've probably heard that from idiots who don't know what they are doing.
The latest version of TWRP works perfectly fine with 4.2 (3G and not). I'm using it on my 3G without any issues.
And the previous 'su' binaries and apk's should be fine. Neither of them should cause any problems with the 3G functionality as they have nothing to do with it. I installed custom recovery and rooted mine the day I got it. Everything is perfect.
Also, absolute worst case scenario, if you do screw something up, it's easy to revert without losing all of your data.
Hmm...I don't consider myself an idiot but did nothing more sinister than root and flash CWM and lost cellular data functionality completely at random two days later (unknown baseband). Had about 6 Android devices before this going back to HTC Hero, flashed all sorts, and never seen anything like it. Eventually had to flash factory image to get it back. Not especially helpful as inexplicable and not reproduced but worth saying nonetheless.
dave_uk said:
Hmm...I don't consider myself an idiot but did nothing more sinister than root and flash CWM and lost cellular data functionality completely at random two days later (unknown baseband). Had about 6 Android devices before this going back to HTC Hero, flashed all sorts, and never seen anything like it. Eventually had to flash factory image to get it back. Not especially helpful as inexplicable and not reproduced but worth saying nonetheless.
Click to expand...
Click to collapse
FYI, there seems to be a sporadic bug in JB on my GNex where on certain reboots it says Unknown Baseband and IMEI in the About menu, and then on the next reboot it's fine. I am wondering if that same bug is cropping up on the N7, and it's just coincidentally happening on some people's devices after rooting, but it goes away later. On my GNex this issue is particularly noticeable if I gave the phone a full reboot from inside software (e.g. using the app Easy Reboot). Whereas a power off / power on does not as frequently run into this issue.
I'm looking forward to getting mine Ordered today and it shipped today! I'm going to give my 16gb (bought in Aug for $249 so no price mod for me ) to either my GF or my daughter. lol
Sorry for the OT post.. I'm just excited. It will be nice to not have to tether my N7 to my phone. I just switched to the shared data plan on AT&T so it will only cost me $10 to add the N7 to my plan
Just fired up my 3g and will root it tomorrow, is there anything really different in rooting this thing vs the 16gb, anything I should watch out for?
kitsunisan said:
Just fired up my 3g and will root it tomorrow, is there anything really different in rooting this thing vs the 16gb, anything I should watch out for?
Click to expand...
Click to collapse
No, they are identical from a rooting perspective. However, they do run slightly different versions of the image, so if you wind up flashing stock, use the right one.
so first my success, i have managed to get root and a TWRP recovery.
now my question in menus im seeing horizontal lines that move with the landscape. so as the phone rotates the screen, the lines also rotate. maybe its just the background design but it seems really awkward to me that they would intend from these lighter brighter lines to be there
if someone would do me a HUGE favor and get me a stock JVP15S recovery? i flashed over mine with CWM before i could back it up and now i have a 34mg OTA update i cant take because of the custom recovery image
death 90 said:
if someone would do me a HUGE favor and get me a stock JVP15S recovery? i flashed over mine with CWM before i could back it up and now i have a 34mg OTA update i cant take because of the custom recovery image
Click to expand...
Click to collapse
I'm not sure that you will find someone who can give you this file, cause it contains all personal data and apps.
death 90 said:
if someone would do me a HUGE favor and get me a stock JVP15S recovery? i flashed over mine with CWM before i could back it up and now i have a 34mg OTA update i cant take because of the custom recovery image
Click to expand...
Click to collapse
I don't have my N7 yet, but on most Androids the stock recovery images do not vary much or at all between minor upgrades, so any stock recovery should be fine. Try the recovery.img inside the JOP40C image straight from Google. https://developers.google.com/android/nexus/images#nakasigjop40c
Worst case if the update still won't take, flash both system and boot from the stock image too (this will unroot you but so would the OTA, and you can fix that later), and then you'll be stock enough for OTAs to work the next time it prompts.
philos64 said:
I'm not sure that you will find someone who can give you this file, cause it contains all personal data and apps.
Click to expand...
Click to collapse
The recovery partition does not contain any personal data or apps. Everything personal is in /data.
philos64 said:
I'm not sure that you will find someone who can give you this file, cause it contains all personal data and apps.
Click to expand...
Click to collapse
im pretty sure the "recovery" partition doesn't contain any of those things. i don't want a stock rom, i need stock a recovery. twrp allows you to back up certain partitions such as boot, cache, and recovery
cmstlist said:
I don't have my N7 yet, but on most Androids the stock recovery images do not vary much or at all between minor upgrades, so any stock recovery should be fine. Try the recovery.img inside the JOP40C image straight from Google. https://developers.google.com/android/nexus/images#nakasigjop40c
Worst case if the update still won't take, flash both system and boot from the stock image too (this will unroot you but so would the OTA, and you can fix that later), and then you'll be stock enough for OTAs to work the next time it prompts.
The recovery partition does not contain any personal data or apps. Everything personal is in /data.
Click to expand...
Click to collapse
i just downloaded that ill try flashing it now i downloaded the "Google Nexus 7 Toolkit" and while it didn't work for me, it did provide a JRo03d stock recovery which i flashed with fastboot and that recovery did not work. when you nexus 7 arrives i believe it would be possible to recover the stock recovery using "fastboot boot twrp-recovery", ALTHOUGH im not sure when you would execute the "backup recovery" if it would read the phones actual partition or the image you uploaded and booted on
cmstlist said:
The recovery partition does not contain any personal data or apps. Everything personal is in /data.
Click to expand...
Click to collapse
Sorry for my quick answer, I haven't seen the "recovery.img". that's file system.zip or tar which contains apps and data for restore
And if you want the Factory image, go to the thread : [Index] All for NEXUS 7 - "nakasig" - (GSM/HSPA+) , it is on, ready for download
ya i grabbed it thanks. what i don't understand is what the 34mg update is for? any ideas? i uploaded two shots, one settings page showing the build mine shipped with and the other is just the update screen i got showing size. Im about to flash the stock ROM from google now. we'll see how goes
the 34mg update was "signed-nakasig-JOP40C-from-JVP15S". i was able to flash the recovery from the stock ROM JOP40C and use that to patch through android and avoid flashing usuing TWRP
death 90 said:
im pretty sure the "recovery" partition doesn't contain any of those things. i don't want a stock rom, i need stock a recovery. twrp allows you to back up certain partitions such as boot, cache, and recovery
i just downloaded that ill try flashing it now i downloaded the "Google Nexus 7 Toolkit" and while it didn't work for me, it did provide a JRo03d stock recovery which i flashed with fastboot and that recovery did not work. when you nexus 7 arrives i believe it would be possible to recover the stock recovery using "fastboot boot twrp-recovery", ALTHOUGH im not sure when you would execute the "backup recovery" if it would read the phones actual partition or the image you uploaded and booted on
Click to expand...
Click to collapse
Honestly don't try toolkits. Just don't, because you don't know what commands or files they are really flashing, and especially because they were written for the wi-fi version. The stock recovery from the wi-fi version is not guaranteed to be compatible with the 3G version.
philos64 said:
Sorry for my quick answer, I haven't seen the "recovery.img". that's file system.zip or tar which contains apps and data for restore
And if you want the Factory image, go to the thread : [Index] All for NEXUS 7 - "nakasig" - (GSM/HSPA+) , it is on, ready for download
Click to expand...
Click to collapse
System.img is also devoid of personal information because to the standard end user it is write-protected. All the personal stuff is in the data partition.
death 90 said:
the 34mg update was "signed-nakasig-JOP40C-from-JVP15S". i was able to flash the recovery from the stock ROM JOP40C and use that to patch through android and avoid flashing usuing TWRP
Click to expand...
Click to collapse
Glad it worked out for you. I had a feeling it was just going to give you JOP40C anyway.
So, I have been trying to root my 3G tablet (JOP40C), but have no luck. I installed TWRP and unlocked just fine using the Google Nexus 7 ToolKit 3.2. When I use the toolkit to root it seems like it is doing everything fine, reboots, and I do not see any errors during the process. However, when I access Titanium backup, or Root Checker it cannot gain root access. I have tried all the options in the toolkit and nothing is working. Can anyone give me some pointers? Thanks!
spongers said:
So, I have been trying to root my 3G tablet (JOP40C), but have no luck. I installed TWRP and unlocked just fine using the Google Nexus 7 ToolKit 3.2. When I use the toolkit to root it seems like it is doing everything fine, reboots, and I do not see any errors during the process. However, when I access Titanium backup, or Root Checker it cannot gain root access. I have tried all the options in the toolkit and nothing is working. Can anyone give me some pointers? Thanks!
Click to expand...
Click to collapse
Yes - Don't use a toolkit!
Since you already have a custom recovery, put the attached file on your sdcard and install it using TWRP. Then you should be good to go.
I'm not sure what is going on but I'm having the following problems and would appreciate any input.
1. Headphones don't always work despite kindle recognizing that they are plugged in (switching to headphones audio profile, and opening stock audio player etc.) and sound is instead routed through the speakers. Sometimes can be fixed by rebooting.
2. Video play back is iffy. When looking up movies through any file browser thumbnails will sometimes not appear, this is the first sign video isn't going to work. When attempting to play any video the player reads the video length as 0:00:00 and won't play. I get an error that says "sorry this video can't be played" or something similar depending on which app I'm using. Sometimes fixed by rebooting.
3. Erased saved game file / erased home screens. Sometimes after rebooting in an attempt to remedy one or both of the above faults I will get the cm notification screen that says "optimizing apps". After full boot most of my 5 home screens will be empty (except for two apps, oddly enough), and my progress for some games is erased. /data/data/ com.blahblahblah
Even if I could find a setting or schedule in titanium backup to "backup all user app data" or a similar app I'd be happy.
I'm not ruling out user error and am in fact hoping that is the problem. I don't want to make the first post super long so I'll post screen shots of settings as I'm asked about them.
Thank you.
JeremySwagS said:
1. Headphones don't always work despite kindle recognizing that they are plugged in (switching to headphones audio profile, and opening stock audio player etc.) and sound is instead routed through the speakers. Sometimes can be fixed by rebooting.
Click to expand...
Click to collapse
I'm not sure, but I think that CM10.1 on the Fire HD is a known issue, due to issues with the kernel.
>>Sent from my homebuilt TARDIS running Android 4.3... Or maybe it's a rooted Kindle Fire HD running ChameleonOS<<
Ph0enix_216 said:
I'm not sure, but I think that CM10.1 on the Fire HD is a known issue, due to issues with the kernel.
>>Sent from my homebuilt TARDIS running Android 4.3... Or maybe it's a rooted Kindle Fire HD running ChameleonOS<<
Click to expand...
Click to collapse
I'm using this kernel. http://i.imgur.com/thu00Y4.png Is there one that would work better? Preferably one with USB otg support.
JeremySwagS said:
I'm using this kernel. http://i.imgur.com/thu00Y4.png Is there one that would work better? Preferably one with USB otg support.
Click to expand...
Click to collapse
I think that there's only two or three kernels available--the stock OS one, and @Maromi has uploaded a couple here. However, I think they are only designed for any ROM with Android 4.2.x.
And none of them support USB OTG. @Hashcode has it on his to-do list, but it's not an easy thing to do.
Hope this helped
EDIT: From your screenshot, it looks like you are running @Hashcode's kernel for his CM10.1 build.
Ph0enix_216 said:
I think that there's only two or three kernels available--the stock OS one, and @Maromi has uploaded a couple here. However, I think they are only designed for any ROM with Android 4.2.x.
And none of them support USB OTG. @Hashcode has it on his to-do list, but it's not an easy thing to do.
Hope this helped
EDIT: From your screenshot, it looks like you are running @Hashcode's kernel for his CM10.1 build.
Click to expand...
Click to collapse
It does help, thank you. I'm running an android 4.2.2 os. (See above screenshot) I want to ensure I'm not making another newb mistake and bricking my kfhd again. (I already did it once... RE: fastboot hell) In your opinion, would it be safe to install one of maromi's kernels?
Is it safe to run the stock kernel with cm10.1?
Glad to hear that Hashcode is working on USB otg support. It was a MAJOR reason I rooted and installed a non stock os.
Edit: I am indeed running Hashcode's 3.0.50+ kernel.
JeremySwagS said:
It does help, thank you. I'm running an android 4.2.2 os. (See above screenshot) I want to ensure I'm not making another newb mistake and bricking my kfhd again. (I already did it once... RE: fastboot hell) In your opinion, would it be safe to install one of maromi's kernels?
Is it safe to run the stock kernel with cm10.1?
Glad to hear that Hashcode is working on USB otg support. It was a MAJOR reason I rooted and installed a non stock os.
Edit: I am indeed running Hashcode's 3.0.50+ kernel.
Click to expand...
Click to collapse
Glad I could help! And yes, bricking any Kindle is a pain in the... well, you know. As for installing kernels, I've never done anything like that, so I can't give you my opinions or advice on it. I do know, however, that like ROMs, you can flash them in TWRP.
Ph0enix_216 said:
Glad I could help! And yes, bricking any Kindle is a pain in the... well, you know. As for installing kernels, I've never done anything like that, so I can't give you my opinions or advice on it. I do know, however, that like ROMs, you can flash them in TWRP.
Click to expand...
Click to collapse
Thanks, I'll check out the forum link you posted for more info.
I need to pick up my flash drive and a few other things tomorrow before I attempt some high techy techy on my kindle. I'll check back then.
JeremySwagS said:
I need to pick up my flash drive and a few other things tomorrow before I attempt some high techy techy on my kindle. I'll check back then.
Click to expand...
Click to collapse
Don't forget to make a backup in TWRP. That way, if something goes wrong, you have a working restore point you can fall back on (I learned this the hard way).
Ph0enix_216 said:
Don't forget to make a backup in TWRP. That way, if something goes wrong, you have a working restore point you can fall back on (I learned this the hard way).
Click to expand...
Click to collapse
The thread you suggested http://forum.xda-developers.com/showthread.php?t=2273172 doesn't have any kernels in the first post and the two links to kernels in the second post have broken links. Any suggestions on where to find an alternative to Hashcode's 3.0.50+ or the stock one?
Also, newb question here. How do I make a backup in twrp? I've only ever used it to flash ROMs and wipe cache and dalvik cache.
JeremySwagS said:
The thread you suggested http://forum.xda-developers.com/showthread.php?t=2273172 doesn't have any kernels in the first post and the two links to kernels in the second post have broken links. Any suggestions on where to find an alternative to Hashcode's 3.0.50+ or the stock one?
Also, newb question here. How do I make a backup in twrp? I've only ever used it to flash ROMs and wipe cache and dalvik cache.
Click to expand...
Click to collapse
No kernels huh? Well. Uh... I can't help you there. Sorry
As for making backups, I can actually help with that. Boot into TWRP. From the main menu, select "Backup." Check-mark every box, and then simply swipe. TWRP will begin backing up your stuff. Just make sure you have a good amount of free space on your SD card. A backup of everything on my Kindle takes up about 3.5 GB. And that's with compression enabled.
>>Sent from my homebuilt TARDIS running Android 4.3... Or maybe it's a rooted Kindle Fire HD running ChameleonOS<<
Ph0enix_216 said:
No kernels huh? Well. Uh... I can't help you there. Sorry
As for making backups, I can actually help with that. Boot into TWRP. From the main menu, select "Backup." Check-mark every box, and then simply swipe. TWRP will begin backing up your stuff. Just make sure you have a good amount of free space on your SD card. A backup of everything on my Kindle takes up about 3.5 GB. And that's with compression enabled.
>>Sent from my homebuilt TARDIS running Android 4.3... Or maybe it's a rooted Kindle Fire HD running ChameleonOS<<
Click to expand...
Click to collapse
Thank you. Done and done!
If anyone finds links to compatible kernels let me know!
Hello, I have a Kindle Fire HD 7" running the downgraded 7.2.3 from KFFA. Then I used Hash's TWRP 2.6.3.1 + 2nd Bootloader thread to get Stock with TWRP but for whatever reason I can't seem to install a ROM that will boot past the "Blue" Logo.
My screen doesn't do the "White haze" that others have mentioned.
Still boots into recovery allowing for wipes + installs.
I have reverted back to 100% stock then made my way back to stock + TWRP three times now, and have looked rather extensively through any threads even somewhat relative to my own problem.
I've been using the Factory fastboot cable to get into fastboot if that makes any difference.
I have downloaded the GAPPs and ROM twice, and I have a very stable connection that hasn't given me issues before.
ROM is the same as from Hash's thread for TWRP + 2nd Bootloader. (cm-10.2-20131115-UNOFFICIAL-tate)
Have tried my cable from my Note 2, Captivate, Epic 4G Touch, and stock KFHD 7" cable as well as the factory fastboot cable.
Kinda stuck, have gone round like this for about 4 hours + now and I must say, the KFHD 7" has been the biggest pain out of any of my Androids by far xD Great tab though.
Any help would be much appreciated. I could always just run stock, but, I'd really like to have CM 4.3 or 4.4 based on my device.
Thanks!
If I left out anything, please, let me know and I will respond ASAP.
veladem said:
Any help would be much appreciated. I could always just run stock, but, I'd really like to have CM 4.3 or 4.4 based on my device.
Thanks!
Click to expand...
Click to collapse
You need to enter TWRP and sideload a ROM. Use this tutorial here http://forum.xda-developers.com/showthread.php?t=2459498
LinearEquation said:
You need to enter TWRP and sideload a ROM. Use this tutorial here http://forum.xda-developers.com/showthread.php?t=2459498
Click to expand...
Click to collapse
Not to be an arse but I don't know how that is going to help 0.o?
My recovery works just fine . . .
veladem said:
Not to be an arse but I don't know how that is going to help 0.o?
My recovery works just fine . . .
Click to expand...
Click to collapse
You have no OS and that's why it won't boot past TWRP. Go into TWRP and adb sideload a ROM onto TWRP and flash it and boot into system. You should probably read a bit before just posting. The link answered your question.
LinearEquation said:
You have no OS and that's why it won't boot past TWRP. Go into TWRP and adb sideload a ROM onto TWRP and flash it and boot into system. You should probably read a bit before just posting. The link answered your question.
Click to expand...
Click to collapse
If I restore my stock rooted OS via TWRP it boots up just fine . . .
The problem I have is after flashing any ROM's I can't get past the blue logo.
But I'll try what you are saying just for kicks.
veladem said:
If I restore my stock rooted OS via TWRP it boots up just fine . . .
The problem I have is after flashing any ROM's I can't get past the blue logo.
But I'll try what you are saying just for kicks.
Click to expand...
Click to collapse
You need to check the zip and make sure it did not get corrupted during the download. Goo.img is updating their servers and downloads can be corrupted. Try downloading from the crackflasher mirror. Make sure it is the ROM for your year and model Kindle Fire HD. You also need to update your TWRP to 2.6.3.1 right away, http://forum.xda-developers.com/showthread.php?t=2128848 Before you flash, factory "swipe" then flash ROM then wipe Dalvik/CACHE then boot into OS. Just drag and drop ROM onto internal SD card before booting into TWRP.
LinearEquation said:
You never said you could access an OS. You simply said you could not get past TWRP. You need to check the zip and make sure it did not get corrupted during the download. Goo.img is updating their servers and downloads can be corrupted. Try downloading from the crackflasher mirror. Make sure it is the ROM for your year and model Kindle Fire HD. You also need to update your TWRP to 2.6.3.1 right away, http://forum.xda-developers.com/showthread.php?t=2128848 Before you flash, factory "swipe" then flash ROM then wipe Dalvik/CACHE then boot into OS.
Click to expand...
Click to collapse
Oh boy lol, let me just correct everywhere you went wrong, cause I've tried to be nice, but I can't let you get away with not even reading the OP.
"You never said you could access an OS." ---> "I could always just run stock"
"You simply said you could not get past TWRP" ---> "Then I used Hash's TWRP 2.6.3.1 + 2nd Bootloader thread to get Stock with TWRP but for whatever reason I can't seem to install a ROM that will boot past the "Blue" Logo." (PS: Being stuck at the "Blue logo" is much different then not being able to boot and being booted into TWRP.)
"You need to check the zip and make sure it did not get corrupted during the download." ---> "I have downloaded the GAPPs and ROM twice, and I have a very stable connection that hasn't given me issues before."
"Goo.img is updating their servers and downloads can be corrupted. Try downloading from the crackflasher mirror." ---> That was where I downloaded from the second+ time I downloaded the ROM.
"Make sure it is the ROM for your year and model Kindle Fire HD." ---> "ROM is the same as from Hash's thread for TWRP + 2nd Bootloader. (cm-10.2-20131115-UNOFFICIAL-tate)"
"You also need to update your TWRP to 2.6.3.1 right away," ---> "Then I used Hash's TWRP 2.6.3.1 + 2nd Bootloader thread to get Stock with TWRP"
So, I just copied and pasted all that from you post, and my OP.
So, let me quote you again from another post you made in my thread.
"You should probably read a bit before just posting." READ THE OP BEFORE TRYING TO HELP MIGHT BE A GOOD IDEA!!! x'D
Thanks for attempting to help though, much appreciated.
veladem said:
Oh boy lol, let me just correct everywhere you went wrong, cause I've tried to be nice, but I can't let you get away with not even reading the OP.
"You never said you could access an OS." ---> "I could always just run stock"
"You simply said you could not get past TWRP" ---> "Then I used Hash's TWRP 2.6.3.1 + 2nd Bootloader thread to get Stock with TWRP but for whatever reason I can't seem to install a ROM that will boot past the "Blue" Logo." (PS: Being stuck at the "Blue logo" is much different then not being able to boot and being booted into TWRP.)
"You need to check the zip and make sure it did not get corrupted during the download." ---> "I have downloaded the GAPPs and ROM twice, and I have a very stable connection that hasn't given me issues before."
"Goo.img is updating their servers and downloads can be corrupted. Try downloading from the crackflasher mirror." ---> That was where I downloaded from the second+ time I downloaded the ROM.
"Make sure it is the ROM for your year and model Kindle Fire HD." ---> "ROM is the same as from Hash's thread for TWRP + 2nd Bootloader. (cm-10.2-20131115-UNOFFICIAL-tate)"
"You also need to update your TWRP to 2.6.3.1 right away," ---> "Then I used Hash's TWRP 2.6.3.1 + 2nd Bootloader thread to get Stock with TWRP"
So, I just copied and pasted all that from you post, and my OP.
So, let me quote you again from another post you made in my thread.
"You should probably read a bit before just posting." READ THE OP BEFORE TRYING TO HELP MIGHT BE A GOOD IDEA!!! x'D
Thanks for attempting to help though, much appreciated.
Click to expand...
Click to collapse
You are screwing up some where. Your doing something wrong. N00bs coming in here and don't read and try and complain about the information posted. Every question you have has been answered a dozen times. Try Google or TMFSE. Quit being lazy.
LinearEquation said:
You are screwing up some where. Your doing something wrong. N00bs coming in here and don't read and try and complain about the information posted. Every question you have has been answered a dozen times. Try Google or TMFSE. Quit being lazy.
Click to expand...
Click to collapse
Well, now you're just flat out being an ass. I've been rooting my phone ever since my G1, definitely not a noob, and I wouldn't have asked for help if I didn't need it and if I hadn't already searched a ton.
I've been here longer then you, just an FYI. Also, your grammar is horrid.
I really wish trolls like you weren't allowed on XDA but man, can't control you guys.
PS: Don't get mad and call me a noob just cause you can't read x'D
EDIT: Linear has been added to my ignore list so if he does reply I don't have an urge to argue with him some more.
Biggest problem here Linear is that you really, really need to learn how to read an OP before posting help.
Thanks!
veladem said:
Well, now you're just flat out being an ass. I've been rooting my phone ever since my G1, definitely not a noob, and I wouldn't have asked for help if I didn't need it and if I hadn't already searched a ton.
I've been here longer then you, just an FYI. Also, your grammar is horrid.
I really wish trolls like you weren't allowed on XDA but man, can't control you guys.
PS: Don't get mad and call me a noob just cause you can't read x'D
EDIT: Linear has been added to my ignore list so if he does reply I don't have an urge to argue with him some more.
Biggest problem here Linear is that you really, really need to learn how to read an OP before posting help.
Thanks!
Click to expand...
Click to collapse
Like I said, do some searching first and you'll get there if you implement some reading skills. For being here so long, you still act like a n00b.
As to the troll comment. I have received 169 thanks in a few short months and you have 17 yet you have been on here here almost 3 years. Way to give back to the community, take a bow.
LinearEquation said:
Like I said, do some searching first and you'll get there if you implement some reading skills. For being here so long, you still act like a n00b.
As to the troll comment. I have received 169 thanks in a few short months and you have 17 yet you have been on here here almost 3 years. Way to give back to the community, take a bow.
Click to expand...
Click to collapse
I give back to the community by offering free Android and iPhone modding in my area, and free support via text and email.
Plus I make sure to tell them to check out the Dev's thread or website and to consider donating to the people who make the magic happen.
The only service I make people pay for is electronic repairs which is a flat rate of $20 + customer buys the parts.
So I think I give back to the community at least a little seeing as I have at the least 20+ people a month asking for help cause some idiot installed a unstable ROM on their phone and 4G vanished or other problems.
By the way, since we are laying our d*cks on the table, might I add that boasting about how many "Likes" you have or "Thanks" isn't something to be proud of, you earned them yes, but don't shove that in other peoples faces, that's just childish.
Thanks again for trying to help.
OK before this turns into a flame war, lemme ask something. Did you factory reset and wipe the system partition before flashing the cm ROM?
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
OK before this turns into a flame war, lemme ask something. Did you factory reset and wipe the system partition before flashing the cm ROM?
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
I did try that yes.
Thank you for helping btw.
It's water under the bridge for me. Would be funny if that were the case though because asking him if he swiped was one of my initial responses to him.
Sent from Nexus 7 flo running SinLess ROM 4.2.2 using xda app-developers app
OK I'm going to reiterate some of what linear said, but in a different way, did you checknthe md5sum of the ROM before you flashed it to make sure it matched up with the one given?
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
OK I'm going to reiterate some of what linear said, but in a different way, did you checknthe md5sum of the ROM before you flashed it to make sure it matched up with the one given?
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Yes sir I did.
OK now for the stupid question, I saw you said it runs a 7.x.x os, just wanted to verify that you are sure of this. I know that kinda a noob question but I have to ask to double check things. Also have you tried flashing cm 11?
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Reiterate
You have a 2012 kfhd
You can get into twrp
Nothing will flash
Odd
We have another person that can't get a restore to take. I've always wondered if it was a formatting issue for him...
But if you were to hand me this kindle I would restore from the restore tool not kffa then I would follow hash codes install 2nd boot loader + twrp thread .
If you've tried that I'm at a loss
Forgive me I read the entire thread but I got lost somewhere in post 3
Sent from my XT907 using xda app-developers app
Sucess! Kinda :/
stunts513 said:
OK now for the stupid question, I saw you said it runs a 7.x.x os, just wanted to verify that you are sure of this. I know that kinda a noob question but I have to ask to double check things. Also have you tried flashing cm 11?
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
I did verify that it is on stock, rooted, de-self updater-ed, 7.2.3. It was on 7.3 something originally.
Hellfire flashed over just fine, CM 10.1 (I think) Flashed it, booted KindleFire (Orange) then (Blue) then Boot logo Booted pretty fast too.
mrkhigh said:
Reiterate
You have a 2012 kfhd
You can get into twrp
Nothing will flash
Odd
We have another person that can't get a restore to take. I've always wondered if it was a formatting issue for him...
But if you were to hand me this kindle I would restore from the restore tool not kffa then I would follow hash codes install 2nd boot loader + twrp thread .
If you've tried that I'm at a loss
Forgive me I read the entire thread but I got lost somewhere in post 3
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
Yes, 2012 KFHD 7" (Tate)
Yes, TWRP works fine.
No, I got Hellfire to flash, but so far nothing else will flash 0.o :/
Also, I did all my restores from KFFA, BUT, I did do a original backup via ADB and did a restore via Fastboot thinking it might have been KFFA but no go still.
And yes, the thread kinda goes to poop cause I was already kinda upset cause this has been the most frastrating Android to work with, and then the pressure got compounded just cause I decided to ask for help :/
If any of this info helps, please let me know, I believe Hellfire is CM 10.1 . . . I believe, that's off the top of my head though.
Thanks!
To be honest I've only installed kinology... Wife won't let me get rid of the kindle os. I didn't really needed kinology but I wanted to update and did not want to reset it up again. He basically ran a neater version of what I was doing.
Is there an error when you flash the ROM and what ROM are you flashing
Sent from my XT907 using xda app-developers app
Ello,
This is my first post!
I've just bought a Asus TF701t and I want to install CROMi-X. I've already done a Nandbackup using CWM booted from fastboot so I still have the stock recovery. However I hear that this tablet allows for a much lower level of backup using APX. Before I do any further changes to this tablet I would like to backup the boot loader.
Is this possible? All the tutorials are for older Transformers.
I'm currently on 10.26.1.18 bootloader with Stock rom.
Thanks...
Read the FAQ
IcePee said:
Ello,
This is my first post!
I've just bought a Asus TF701t and I want to install CROMi-X. I've already done a Nandbackup using CWM booted from fastboot so I still have the stock recovery. However I hear that this tablet allows for a much lower level of backup using APX. Before I do any further changes to this tablet I would like to backup the boot loader.
Is this possible? All the tutorials are for older Transformers.
I'm currently on 10.26.1.18 bootloader with Stock rom.
Thanks...
Click to expand...
Click to collapse
Ooops, I just read: http://forum.xda-developers.com/showthread.php?t=2554744. Doh! Newbie mistake.
This leads to my next question Does anyone know if we will be getting this feature?
IcePee said:
Ooops, I just read: http://forum.xda-developers.com/showthread.php?t=2554744. Doh! Newbie mistake.
This leads to my next question Does anyone know if we will be getting this feature?
Click to expand...
Click to collapse
It took a very long time to get nvflash working on Android 4.2.1 on the TF201, TF300 and TF700. As we have fewer devs working on the TF701 I would say you have zero chance of seeing anything insode the next 6 months.
As long as you follow the guides it is hard to brick. If unsure ask first And NEVER wipe from the BOOTLOADER. EVER.
OK, going for it
sbdags said:
It took a very long time to get nvflash working on Android 4.2.1 on the TF201, TF300 and TF700. As we have fewer devs working on the TF701 I would say you have zero chance of seeing anything insode the next 6 months.
As long as you follow the guides it is hard to brick. If unsure ask first And NEVER wipe from the BOOTLOADER. EVER.
Click to expand...
Click to collapse
Thanks for getting back to me this quickly.
OK, I'm going for it! I've already done a wipe data/factory reset and wipe cache partition. Let's see where we get to...
Result!
Just to let you know I've successfully installed the CROMi-X firmware. It went very smoothly once I could get it going. I kept having problems installing from the keyboard dock's SDCard reader. It kept failing the initial checksum process. I switched to a higher capacity MicroSD in the internal reader and it went on without a hitch.
I just bought myself an almost mint condition Nexus 6 (build MRA58R). It's running Marshmallow and I tried rooting it today. After I researched how to go by obtaining root I tried it out, felt very confident, didn't come across any errors. But then when I was booting back up, a screen with red letters saying something about my phone being corrupted was not allowing my phone to boot. Naturally, first I panicked. Afterwards I researched, found and then executed a manual flash of system, boot, bootloader, cache and recovery images. Then, my phone was back up and running. Discouraged and defeated, here I am knowing I could've done some better things with my time than mash commands into a terminal to fix my nooby mistake for a few hours. How should I approach obtaining root on my phone if at all possible with my model?
meeniemuffin said:
.... But then when I was booting back up, a screen with red letters saying something about my phone being corrupted was not allowing my phone to boot.
Click to expand...
Click to collapse
You could bring Google to court when your device is working 100% and the message says it is corrupt. Read the OP of this link. http://forum.xda-developers.com/showthread.php?t=3059493
meeniemuffin said:
I just bought myself an almost mint condition Nexus 6 (build MRA58R). It's running Marshmallow and I tried rooting it today. After I researched how to go by obtaining root I tried it out, felt very confident, didn't come across any errors. But then when I was booting back up, a screen with red letters saying something about my phone being corrupted was not allowing my phone to boot. Naturally, first I panicked. Afterwards I researched, found and then executed a manual flash of system, boot, bootloader, cache and recovery images. Then, my phone was back up and running. Discouraged and defeated, here I am knowing I could've done some better things with my time than mash commands into a terminal to fix my nooby mistake for a few hours. How should I approach obtaining root on my phone if at all possible with my model?
Click to expand...
Click to collapse
-enable "OEM unlocking" in developer options
-unlock bootloader
-flash TWRP using fastboot
-flash a custom kernel
-flash SuperSU 2.52
-KEEP BOOTLOADER UNLOCKED
-KEEP "OEM unlocking" ENABLED
---------- Post added at 09:50 AM ---------- Previous post was at 09:42 AM ----------
NLBeev said:
You could bring Google to court when your device is working 100% and the message says it is corrupt. Read the OP of this link. http://forum.xda-developers.com/showthread.php?t=3059493
Click to expand...
Click to collapse
There's nothing mentioned there.
Droidphilev said:
There's nothing mentioned there.
Click to expand...
Click to collapse
Hmm, here the links works. It is a link to a stock rom that is already rooted.
The rom is updated with the latest security OTA.
Full name of the OP.
[ROM]【6.0_r3】Stock MRA58R [Lite] - 【Marshmallow】【hC kernel】- 11/05/15
NLBeev said:
Hmm, here the links works. It is a link to a stock rom that is already rooted.
The rom is updated with the latest security OTA.
Full name of the OP.
[ROM]【6.0_r3】Stock MRA58R [Lite] - 【Marshmallow】【hC kernel】- 11/05/15
Click to expand...
Click to collapse
It indeed works but i thought it would bring to a page about the court thing you have mentioned.
Droidphilev said:
It indeed works but i thought it would bring to a page about the court thing you have mentioned.
Click to expand...
Click to collapse
No I was joking, sorry. But there is something serious behind the joke.
Here on XDA there are too many posts/questions about the 'corrupt message'.
The distance between ' customizing the phone' and 'Google' is growing.
NLBeev said:
No I was joking, sorry. But there is something serious behind the joke.
Here on XDA there are too many posts/questions about the 'corrupt message'.
The distance between ' customizing the phone' and 'Google' is growing.
Click to expand...
Click to collapse
Aha! i saw you posting this before but never knew that it was a joke
I didn't even need to read all this stuff. First thing I did was get into developer mode and almost instinctual that I turned on OEM unlocking before setting about unlocking the bootloader.
Sent from my Nexus 6 using Tapatalk
Yeah I bought my N6 recently and had a bad first time experience too. I ended up using a toolkit to root and all that, didn't need a custom rom so I kept it stock with TWRP and I'm very happy. Since then, I rooted some of the old devices I had laying around (you can check my signature), so I should be more prepared next time I need to update. My problem is I didn't really understand the commands, what did what and what exactly was required for root. Now that I have had plenty to practice with I'm pretty comfortable with commands and recoveries. Practice makes perfect I guess
NLBeev said:
No I was joking, sorry. But there is something serious behind the joke.
Here on XDA there are too many posts/questions about the 'corrupt message'.
The distance between ' customizing the phone' and 'Google' is growing.
Click to expand...
Click to collapse
Pretty much the trend. I bet by Android 7.0, rooting will be impossible.
shadowcore said:
Pretty much the trend. I bet by Android 7.0, rooting will be impossible.
Click to expand...
Click to collapse
I hope not. Google's software and design will be the weak point. Google could not give us some simple options like a dark interface, reboot options and dpi settings.
So, people, to sum it all up... The road to obtaining root on this Marshmallow enabled phone is?
If bootload is locked, unlock it - This will erase everything backup your device
1. Get modified boot.img for your version, flash it
2. Flash twrp
3. Flash SuperSu 2.52
meeniemuffin said:
So, people, to sum it all up... The road to obtaining root on this Marshmallow enabled phone is?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=63999613&postcount=3
!!!
Droidphilev said:
http://forum.xda-developers.com/showpost.php?p=63999613&postcount=3
!!!
Click to expand...
Click to collapse
Sorry! Slow to learn over here. I still have a question...do I need a custom kernel and flash stock rom? Or just a custom stock ROM thats already prerooted? Both, perhaps? Would I have to flash Twrp in order to even do this?
meeniemuffin said:
Sorry! Slow to learn over here. I still have a question...do I need a custom kernel and flash stock rom? Or just a custom stock ROM thats already prerooted? Both, perhaps? Would I have to flash Twrp in order to even do this?
Click to expand...
Click to collapse
You have a stockrom now, right?
if you want to keep that for now then this is the easiest way. The TWRP step is there to be able to flash the custom kernel. (and of course make backups and flash other roms in the future)
Droidphilev said:
You have a stockrom now, right?
if you want to keep that for now then this is the easiest way. The TWRP step is there to be able to flash the custom kernel. (and of course make backups and flash other roms in the future)
Click to expand...
Click to collapse
I had an epiphany earlier. I did everything....it all hit me at once. I finally managed to get Pure Nexus ROM working. Time for a test drive.
Thanks for the advice.
meeniemuffin said:
I had an epiphany earlier. I did everything....it all hit me at once. I finally managed to get Pure Nexus ROM working. Time for a test drive.
Thanks for the advice.
Click to expand...
Click to collapse
enjoy!
but DO NOT forget to keep "OEM unlocking" enabled!
(it will save you when you ever get locked out from your google acoount because you became aflashoholic)