I have a China version OPO in hand, 64G storage. But after flashing the new CM11S, the storage reduced to 16G. I suspect it's CM11S re partitioned the storage, and didn't considering there are 64G version!
Is this mean I have to wait for the even newer CM to repair it?
I downloaded the firmware here: http://forum.xda-developers.com/showthread.php?t=2765455
liujunwei4321 said:
I have a China version OPO in hand, 64G storage. But after flashing the new CM11S, the storage reduced to 16G. I suspect it's CM11S re partitioned the storage, and didn't considering there are 64G version!
Is this mean I have to wait for the even newer CM to repair it?
I downloaded the firmware here: http://forum.xda-developers.com/showthread.php?t=2765455
Click to expand...
Click to collapse
You flashed the firmware files of the 16 GB version, meaning you also flashed the partition table of the 16 GB version. If you got no backup, I think you'll have to wait for a dump of these files from a 64 GB phone to fix it for you or to manually edit the file containing the partition table. But be very careful with that... You can easily brick your device if you are not really knowing what you are doing.
dansou901 said:
You flashed the firmware files of the 16 GB version, meaning you also flashed the partition table of the 16 GB version. If you got no backup, I think you'll have to wait for a dump of these files from a 64 GB phone to fix it for you or to manually edit the file containing the partition table. But be very careful with that... You can easily brick your device if you are not really knowing what you are doing.
Click to expand...
Click to collapse
Do you know which file define the partition table?
liujunwei4321 said:
Do you know which file define the partition table?
Click to expand...
Click to collapse
As I don't have the phone yet, no. You'll have to ask the uploader of the files about it.
dansou901 said:
As I don't have the phone yet, no. You'll have to ask the uploader of the files about it.
Click to expand...
Click to collapse
I'll try
Any updates on this? Might be getting my hands-on a China 64GB OPO soon too!
liujunwei4321 said:
I have a China version OPO in hand, 64G storage. But after flashing the new CM11S, the storage reduced to 16G. I suspect it's CM11S re partitioned the storage, and didn't considering there are 64G version!
Is this mean I have to wait for the even newer CM to repair it?
I downloaded the firmware here: http://forum.xda-developers.com/showthread.php?t=2765455
Click to expand...
Click to collapse
http://forums.oneplus.net/threads/af...ge-12#post-231
Check private msg over there. DavidS sent you info on how to flash the latest build of CM11S.
reply
LordKuroda said:
Any updates on this? Might be getting my hands-on a China 64GB OPO soon too!
Click to expand...
Click to collapse
No update up to now.
others
Check private msg over there. DavidS sent you info on how to flash the latest build of CM11S.[/QUOTE]
I did. But the problem remains. He said next update will solve the problem.
liujunwei4321 said:
Check private msg over there. DavidS sent you info on how to flash the latest build of CM11S.
Click to expand...
Click to collapse
I did. But the problem remains. He said next update will solve the problem.
Click to expand...
Click to collapse
Check the post I made in that thread. Go into TWRP and do a FULL userdata format. (You can "fastboot boot" TWRP without flashing it if you wish, or you can flash it.)
Wipe->Advanced Wipe->Data
(the standard factory reset will just remove all files outside of /data/media without reformatting the partition.)
Based on your description of what you did to flash it, I'm fairly certain that your partition table is OK (since it doesn't look like you altered that), but you flashed a premade 16GB userdata image to a 64GB partition.
Entropy512 said:
I did. But the problem remains. He said next update will solve the problem.
Click to expand...
Click to collapse
Check the post I made in that thread. Go into TWRP and do a FULL userdata format. (You can "fastboot boot" TWRP without flashing it if you wish, or you can flash it.)
Wipe->Advanced Wipe->Data
(the standard factory reset will just remove all files outside of /data/media without reformatting the partition.)
Based on your description of what you did to flash it, I'm fairly certain that your partition table is OK (since it doesn't look like you altered that), but you flashed a premade 16GB userdata image to a 64GB partition.[/QUOTE]
Anyone successfully flashed the Build XNPH22Q on a Chinese 64GB OPO and could still use the full 64GB? I couldn't open the thread on the OPO forum. Does flashing each of the images image.zip work?
WenLei said:
Check the post I made in that thread. Go into TWRP and do a FULL userdata format. (You can "fastboot boot" TWRP without flashing it if you wish, or you can flash it.)
Wipe->Advanced Wipe->Data
(the standard factory reset will just remove all files outside of /data/media without reformatting the partition.)
Based on your description of what you did to flash it, I'm fairly certain that your partition table is OK (since it doesn't look like you altered that), but you flashed a premade 16GB userdata image to a 64GB partition.
Click to expand...
Click to collapse
[/QUOTE]Anyone successfully flashed the Build XNPH22Q on a Chinese 64GB OPO and could still use the full 64GB? I couldn't open the thread on the OPO forum. Does flashing each of the images image.zip work?[/QUOTE]
I've done what you said and my 64G OPO "turns" into 16G. I get information from OPO staff that CM will push an OTA this week to fix this issue.So just be patient.
Anyone successfully flashed the Build XNPH22Q on a Chinese 64GB OPO and could still use the full 64GB? I couldn't open the thread on the OPO forum. Does flashing each of the images image.zip work?[/QUOTE]
I've done what you said and my 64G OPO "turns" into 16G. I get information from OPO staff that CM will push an OTA this week to fix this issue.So just be patient.[/QUOTE]
Thanks for the info, I will be receiving my 64GB tomorrow! :good:
ailai55 said:
Anyone successfully flashed the Build XNPH22Q on a Chinese 64GB OPO and could still use the full 64GB? I couldn't open the thread on the OPO forum. Does flashing each of the images image.zip work?
Click to expand...
Click to collapse
I've done what you said and my 64G OPO "turns" into 16G. I get information from OPO staff that CM will push an OTA this week to fix this issue.So just be patient.
Click to expand...
Click to collapse
What I said, or what he said?
Flashing a 16GB userdata.img is going to cause exactly this problem - have you tried the recovery reformat approach?
Entropy512 said:
What I said, or what he said?
Flashing a 16GB userdata.img is going to cause exactly this problem - have you tried the recovery reformat approach?
Click to expand...
Click to collapse
Sorry, I might mis-quoted your post.Actually I intended to reply his post.
I haven't done anything yet because I am waiting for CM's next update.
ailai55 said:
Sorry, I might mis-quoted your post.Actually I intended to reply his post.
I haven't done anything yet because I am waiting for CM's next update.
Click to expand...
Click to collapse
Hello everyone, I got my one plus one today! I confirm CM11S rom works on 64GB. See Attached!
This is what I did with my phone and feel very excited now!
1. Unlock the phone by
fastboot oem unlock
2. Flash the recovery and modem with WCDMA
fastboot.exe flash recovery recovery.img
fastboot flash modem NON-HLOS.bin
3. Flash XNPH22Q
Reboot to recovery, apply factory reset and install the XNPH22Q zip rom file
You can find the necessary files and instruction here if you know Chinese. Assume you have played with another phone before, it's easy!
[recovery and hacked modem] oneplusbbs.com/forum.php?mod=viewthread&tid=336574&extra=page%3D3%26filter%3Dtypeid%26typeid%3D25
[latest CM12s rom] oneplusbbs.com/forum.php?mod=viewthread&tid=351823&extra=page%3D1%26filter%3Dtypeid%26typeid%3D28
Cheers!
ailai55 said:
Sorry, I might mis-quoted your post.Actually I intended to reply his post.
I haven't done anything yet because I am waiting for CM's next update.
Click to expand...
Click to collapse
An update is not going to do anything unless they release a separate package with 64GB userdata, or force a complete format on OTA (generally this is something people don't do...)
If the update also has a 16GB userdata partition image, it'll have the exact same problem. Formatting userdata in recovery will resize it to use the entire partition.
sasalove said:
Hello everyone, I got my one plus one today! I confirm CM11S rom works on 64GB. See Attached!
This is what I did with my phone and feel very excited now!
1. Unlock the phone by
fastboot oem unlock
2. Flash the recovery and modem with WCDMA
fastboot.exe flash recovery recovery.img
fastboot flash modem NON-HLOS.bin
3. Flash XNPH22Q
Reboot to recovery, apply factory reset and install the XNPH22Q zip rom file
You can find the necessary files and instruction here if you know Chinese. Assume you have played with another phone before, it's easy!
[recovery and hacked modem] oneplusbbs.com/forum.php?mod=viewthread&tid=336574&extra=page%3D3%26filter%3Dtypeid%26typeid%3D25
[latest CM12s rom] oneplusbbs.com/forum.php?mod=viewthread&tid=351823&extra=page%3D1%26filter%3Dtypeid%26typeid%3D28
Cheers!
Click to expand...
Click to collapse
Key thing here: No flashing of userdata.img in fastboot - that's likely the ONLY thing you need to do (or more specifically in this case, NOT do) in order to avoid the issue of 64GB devices reporting 16GB userdata.
sasalove said:
Hello everyone, I got my one plus one today! I confirm CM11S rom works on 64GB. See Attached!
This is what I did with my phone and feel very excited now!
1. Unlock the phone by
fastboot oem unlock
2. Flash the recovery and modem with WCDMA
fastboot.exe flash recovery recovery.img
fastboot flash modem NON-HLOS.bin
3. Flash XNPH22Q
Reboot to recovery, apply factory reset and install the XNPH22Q zip rom file
You can find the necessary files and instruction here if you know Chinese. Assume you have played with another phone before, it's easy!
[recovery and hacked modem] oneplusbbs.com/forum.php?mod=viewthread&tid=336574&extra=page%3D3%26filter%3Dtypeid%26typeid%3D25
[latest CM12s rom] oneplusbbs.com/forum.php?mod=viewthread&tid=351823&extra=page%3D1%26filter%3Dtypeid%26typeid%3D28
Cheers!
Click to expand...
Click to collapse
Thank you. In your third step, could you make it more clear how did you do it? Did you flash the 467MB zip in recovery or followed the instructions in the original thread ( zip first and type commands)?
ailai55 said:
Thank you. In your third step, could you make it more clear how did you do it? Did you flash the 467MB zip in recovery or followed the instructions in the original thread ( zip first and type commands)?
Click to expand...
Click to collapse
Flashing the zip rom is sufficient, no other command needed. Note you need to perform "Factory Reset" when you boot to recovery then apply zip rom. Cheers! :laugh:
reply to s
sasalove said:
Hello everyone, I got my one plus one today! I confirm CM11S rom works on 64GB. See Attached!
This is what I did with my phone and feel very excited now!
1. Unlock the phone by
fastboot oem unlock
2. Flash the recovery and modem with WCDMA
fastboot.exe flash recovery recovery.img
fastboot flash modem NON-HLOS.bin
3. Flash XNPH22Q
Reboot to recovery, apply factory reset and install the XNPH22Q zip rom file
You can find the necessary files and instruction here if you know Chinese. Assume you have played with another phone before, it's easy!
[recovery and hacked modem] oneplusbbs.com/forum.php?mod=viewthread&tid=336574&extra=page%3D3%26filter%3Dtypeid%26typeid%3D25
[latest CM12s rom] oneplusbbs.com/forum.php?mod=viewthread&tid=351823&extra=page%3D1%26filter%3Dtypeid%26typeid%3D28
Cheers!
Click to expand...
Click to collapse
Could you post more detailed procedures? I couldn't get it work!
Related
One of my friends BRICK his phone and he has no idea how. He has a rooted HTC ONE X on AT&T network with Viper XL (Not even sure what version of the ROM) probably from last december.
It is now stuck on the Booting animation screen and won't get passed that. I am able to access TWRP recovery, but there is not zip files or backups any longer. When I originally flashed this phone for him I had a zip file on the root of the internal SD CARD. It no longer is there and i have not rooted/flashed a phone for almost a year and can't remember.
I tried to fastboot oem lock and it fails (was thinking i could some how get it to boot and install stock jelly bean)
I am able to mount the SD card via TWRP and throw a rom in there via zip, but when i unmount i and go to restore or install i do not see any zip. When I mount again the file i put in the phone no longer exists.
Is there a work around or another way to flash any custom room. I was thinking of CM10 nightly evita... I don't care what rom as long as i can get the phone working again for him.
Is there a way to flash a rom the way we flash boot.img via fastboot where the files can reside on the PC and not the phone? Any assistance/tips would be great. Again i don't care which rom I flash and i have TWRP recovery access. Currently i have CM10 downloaded if hat helps. Thank you in advanced
Is there anything showing up on the sd card at all in TWRP? You could try formatting the sd card in Windows and trying to move a ROM over again.
Sent from my Evita
timmaaa said:
Is there anything showing up on the sd card at all in TWRP? You could try formatting the sd card in Windows and trying to move a ROM over again.
Sent from my Evita
Click to expand...
Click to collapse
Im able to see folders and stuff like the typical android folders. So you are saying i should mount the SD card/try to format the sd card via windows then try to put a zip file in there to see if i can access it? Question.. All i would need to do is flash the boot.img first via fastboot then install the zip via twrp right?
Yeah that's what I mean. Most people flash the boot.img afterwards but I believe you can do it before flashing the ROM.
Sent from my Evita
timmaaa said:
Yeah that's what I mean. Most people flash the boot.img afterwards but I believe you can do it before flashing the ROM.
Sent from my Evita
Click to expand...
Click to collapse
When i format the sd card does it need to be FAT32? What format?
Yep, fat32 is the right format.
Sent from my Evita
timmaaa said:
Yep, fat32 is the right format.
Sent from my Evita
Click to expand...
Click to collapse
Weird i get the same results as before. I formatted the SD card via fat32, through the zip in there, then I unmount the sd card so i can get back to twrp menus to install and android folders are back, but no zip. I am able to successfully copy the cm10 zip there so i don't get it.
Which version of TWRP are you using? And what process are you following when wiping before the flash?
Sent from my Evita
Sounds similar to what happened to me when i did factory reset in bootloader. Others seem to be able to just format in pc and have it work in recovery but it didn't work for me so i just ruu'd to fix it. Since it might have been awhile since you setup his phone you might as well s-off the phone then run latest jb ruu so you have flash latest cm10.1 nightlies which also no longer needs touchscreen downgrade. Afterwards flash latest twrp 2.6.0.0 and copy rom of choice to sdcard and flash.
How will he s-off if he can't boot into the OS?
Sent from my Evita
timmaaa said:
Which version of TWRP are you using? And what process are you following when wiping before the flash?
Sent from my Evita
Click to expand...
Click to collapse
TWRP version 2.3.1.0
Weird I never had issues before and fyi this phone used to be mine so i did all the flashing originally then sold it to a friend of mine and he refused to go back to stock and preferred to stay with viper xl. Now i'm trying to help him out, any thoughts?
DvineLord said:
Sounds similar to what happened to me when i did factory reset in bootloader. Others seem to be able to just format in pc and have it work in recovery but it didn't work for me so i just ruu'd to fix it. Since it might have been awhile since you setup his phone you might as well s-off the phone then run latest jb ruu so you have flash latest cm10.1 nightlies which also no longer needs touchscreen downgrade. Afterwards flash latest twrp 2.6.0.0 and copy rom of choice to sdcard and flash.
Click to expand...
Click to collapse
That's the problem I downloaded the latest RUU from HTC and I don't have a way to flash it or else I would have. Not sure what else I can do here. Anyone have any ideas what I can try next or is this consider a Permanently bricked phone? If it is then i don't want to spend time on it as I have already dedicated over 2 hrs, thanks.
XsMagical posted a fix for corrupted sd cards on this forum a while back, you could give that a try.
Sent from my Evita
timmaaa said:
XsMagical posted a fix for corrupted sd cards on this forum a while back, you could give that a try.
Sent from my Evita
Click to expand...
Click to collapse
So that's what it probably is a corrupted SD CARD? Thanks I will search his posts.
Yeah that's my best guess. It does seem odd that you can still view the Android folders from within recovery though. When you copy something from your pc across does it definitely succeed? I had a wild thought earlier that maybe it had been formatted as read only or something like that.
Sent from my Evita
timmaaa said:
Yeah that's my best guess. It does seem odd that you can still view the Android folders from within recovery though. When you copy something from your pc across does it definitely succeed? I had a wild thought earlier that maybe it had been formatted as read only or something like that.
Sent from my Evita
Click to expand...
Click to collapse
Yeah it successfully completes and I am able to see the file there. Even if i remove the USB cable without unmounting and then plug it back the file is still there. It's when I unmount from TWRP when it then vanishs. I found the article from the guy who wrote a tutorial on how to fix corrupted SD cards, but the link is now broken and no longer exists, doh!
Have you tried upgrading to TWRP 2.6? Not sure if it's gonna help, but anything is worth a try at this stage, right?
Sent from my Evita
timmaaa said:
Have you tried upgrading to TWRP 2.6? Not sure if it's gonna help, but anything is worth a try at this stage, right?
Sent from my Evita
Click to expand...
Click to collapse
Sure it's worth a try. How do i upgrade twrp? It's been a while. Is it just flashing via fastboot? BC if it's a zip remember I can't do that.
Download it from here. Put it in your fastboot folder. Issue these fastboot commands:
fastboot flash recovery "recovery.img"
(whatever the exact filename is, minus the talking marks)
fastboot erase cache
fastboot reboot-bootloader
Now you can enter recovery from your phone screen.
Sent from my Evita
timmaaa said:
Download it from here. Put it in your fastboot folder. Issue these fastboot commands:
fastboot flash recovery "recovery.img"
(whatever the exact filename is, minus the talking marks)
fastboot erase cache
fastboot reboot-bootloader
Now you can enter recovery from your phone screen.
Sent from my Evita
Click to expand...
Click to collapse
Great thanks.
Not sure what's going on here. CM nightlies. Didn't notice until I got a space warning. It used to be like 50 something when I was on stock.
X10D3 said:
Not sure what's going on here. CM nightlies. Didn't notice until I got a space warning. It used to be like 50 something when I was on stock.
Click to expand...
Click to collapse
You accidentally flashed the userdata.img for 16 GB version which repartitioned your data partition. You have to flash the userdata64.img to get it to old state again. As I don't have the phone yet, I can't help you further.
dansou901 said:
You accidentally flashed the userdata.img for 16 GB version which repartitioned your data partition. You have to flash the userdata64.img to get it to old state again. As I don't have the phone yet, I can't help you further.
Click to expand...
Click to collapse
Are the CM nightlies based off the 16gb variant?
X10D3 said:
Are the CM nightlies based off the 16gb variant?
Click to expand...
Click to collapse
No, but apparently they've got the userdata.img files inside the zip (I don't know why). So please open the zip you are flashing and take a look at what you are actually flashing (including the flashing script).
Yep, you flashed the 16gb version.
Sent from my One using XDA Free mobile app
Ah, I see you found the problem was using a toolkit... That's why I never used toolkits I didn't create myself or have looked at thoroughly first!
dansou901 said:
Ah, I see you found the problem was using a toolkit... That's why I never used toolkits I didn't create myself or have looked at thoroughly first!
Click to expand...
Click to collapse
I was looking for easy. Already scripted. Fixed and ready to roll. I didn't even think about there being 2 userdata files. Monday...
How did you fixed this?
Ive got the same problem
I've found the userdata64G.img
but when i do:
fastboot flash recovery userdata64G.img it gives an error
when i do fastboot flash recovery userdata.img it also gives the same error -> ive renamed the file
--> error is : Size to big
how do i fix this problem
Fopflugel said:
How did you fixed this?
Ive got the same problem
I've found the userdata64G.img
but when i do:
fastboot flash recovery userdata64G.img it gives an error
when i do fastboot flash recovery userdata.img it also gives the same error -> ive renamed the file
--> error is : Size to big
how do i fix this problem
Click to expand...
Click to collapse
It stopped you becasue that would have bricked your phone, don't type fastboot commands without knowing what to do.
What you're telling fastboot to do is to override the recovery with a userdata which would have for sure bricked your phone.
You want to be doing fastboot flash userdata userdata64G.img
not flashing recovery.
16 to 64
dansou901 said:
You accidentally flashed the userdata.img for 16 GB version which repartitioned your data partition. You have to flash the userdata64.img to get it to old state again. As I don't have the phone yet, I can't help you further.
Click to expand...
Click to collapse
Hello friends,
I'm not a technician and I have the same problem with the memory.
Can someone explain step by step how do I fix my phone?
Thanks in advance!
Maldavanin said:
Hello friends,
I'm not a technician and I have the same problem with the memory.
Can someone explain step by step how do I fix my phone?
Thanks in advance!
Click to expand...
Click to collapse
1. Download 64gb userdata (find it)
2. Flash it via fastboot.
Google on how to use fastboot.
Requires unlocked bootloader
The small little details are up to you and can be found in various stickied threads. Best of luck.
try flash this stock ColorOS from here http://forum.xda-developers.com/showthread.php?t=2772627
I know this is the wrong place to post this, but everywhere else tells I can't. So here goes:
I've a T300 with AndroidBlue 3.0 and JB 4.1.1 on nit. Web browsing is typically slow.
I need to up TWRP from 2.2 to the latest and greatest, and would like some input as to whether or not going with CM 10.1 would help my "Browsing Experience"?
It seems that Rom Toolbox would take care of installing CM (or from TWRP), and TWRP Manager (with the right file - it dl's the ICS version) would take care of that.
Correct?
I'm sure this has been discussed before, but searching has yielded pages and pages that do not help.
All help have my thanks in advance.
RBraverman said:
I know this is the wrong place to post this, but everywhere else tells I can't. So here goes:
I've a T300 with AndroidBlue 3.0 and JB 4.1.1 on nit. Web browsing is typically slow.
I need to up TWRP from 2.2 to the latest and greatest, and would like some input as to whether or not going with CM 10.1 would help my "Browsing Experience"?
It seems that Rom Toolbox would take care of installing CM (or from TWRP), and TWRP Manager (with the right file - it dl's the ICS version) would take care of that.
Correct?
I'm sure this has been discussed before, but searching has yielded pages and pages that do not help.
All help have my thanks in advance.
Click to expand...
Click to collapse
OK so first you have to update that ancient bootloader of yours to use KitKat. Do that by flashing the latest Stock ROM via fastboot.
cmendonc2 said:
OK so first you have to update that ancient bootloader of yours to use KitKat. Do that by flashing the latest Stock ROM via fastboot.
Click to expand...
Click to collapse
Thank you for answering - I've been ill since I wrote that, so I'm finally getting back to you. I'm looking at ASUS's site, as I can not find my build number (AndroidBlue over-wrote that in status) - but this is a US version, so I'm assuming 10.6.1.27.1 US SKU?
Can I not flash this via TRWP - I'm assuming Fastboot, just as when I flashed TWRP.
When I flash this will everything be back to stock: no root, no TWRP?
RBraverman said:
Thank you for answering - I've been ill since I wrote that, so I'm finally getting back to you. I'm looking at ASUS's site, as I can not find my build number (AndroidBlue over-wrote that in status) - but this is a US version, so I'm assuming 10.6.1.27.1 US SKU?
Can I not flash this via TRWP - I'm assuming Fastboot, just as when I flashed TWRP.
When I flash this will everything be back to stock: no root, no TWRP?
Click to expand...
Click to collapse
Hope you get getter
10.6.1.27.1 Will work, and I suggest flashing with fastboot so you can confirm that fastboot works so you can reflash TWRP later. When you do flash the 10.6.1.27.1 stock, everything will be erased, including TWRP, so you will have to flash a newer version of TWRP. That can be the stable branch here: http://forum.xda-developers.com/showthread.php?t=2772093
cmendonc2 said:
Hope you get getter
Click to expand...
Click to collapse
Thank you, slowly on the mend.
cmendonc2 said:
10.6.1.27.1 Will work, and I suggest flashing with fastboot so you can confirm that fastboot works so you can reflash TWRP later. When you do flash the 10.6.1.27.1 stock, everything will be erased, including TWRP, so you will have to flash a newer version of TWRP. That can be the stable branch here: http://forum.xda-developers.com/showthread.php?t=2772093
Click to expand...
Click to collapse
I don't see the "THANKS" button.......
Ok, so if I do this I LITERALLY start over, and should ASUS up another F/W version, I do this all over - correct?
Here's the REAL crux of the matter; I like the unit as it is EXCEPT that half the day the wifi sucks, either via 3g phone or RV park WiFi which I built! I'm getting closer to the reason for this, close my Dell 6400 down and the WiFi gets better, so interference.
OVERALL, would upping this one (I have 2) make any perceptible difference on the WiFi? I mean all else is fine.
So I need 3 things: newest F/W (have), Latest TWRP(don't have - yet but looking, 2.7 I believe), latest way to root(don't know) - Correct?
Again where is that thanks button!!!!!
RBraverman said:
I don't see the "THANKS" button.......
Ok, so if I do this I LITERALLY start over, and should ASUS up another F/W version, I do this all over - correct?
Here's the REAL crux of the matter; I like the unit as it is EXCEPT that half the day the wifi sucks, either via 3g phone or RV park WiFi which I built! I'm getting closer to the reason for this, close my Dell 6400 down and the WiFi gets better, so interference.
OVERALL, would upping this one (I have 2) make any perceptible difference on the WiFi? I mean all else is fine.
Again where is that thanks button!!!!!
Click to expand...
Click to collapse
Thanks button is below the username at the end of the post
Upping the tf300 would make the pages load faster on the tablet after they have downloaded, and would make Chrome or whatever other browser you are using load the page much faster. It would unlikely change the download speed to the tablet.
It's also unlikely that Asus will release another FW version because the tf300 is already 2 or 3 years old and they tend to cut support after that time. Then again, they could release an update tomorrow for no reason, but that doesn't mean the bootloader has to change requiring you to flash stock again. I updated my stock FW a more than a year ago and there has been 2 or 3 updates since that, but the bootloader hasn't changed so I haven't done any of those updates.
cmendonc2 said:
Thanks button is below the username at the end of the post
Upping the tf300 would make the pages load faster on the tablet after they have downloaded, and would make Chrome or whatever other browser you are using load the page much faster. It would unlikely change the download speed to the tablet.
It's also unlikely that Asus will release another FW version because the tf300 is already 2 or 3 years old and they tend to cut support after that time. Then again, they could release an update tomorrow for no reason, but that doesn't mean the bootloader has to change requiring you to flash stock again. I updated my stock FW a more than a year ago and there has been 2 or 3 updates since that, but the bootloader hasn't changed so I haven't done any of those updates.
Click to expand...
Click to collapse
NOW it's there!
Okay upping to stock F/W, looking for TWRP (openrecovery-twrp-2.6.3.0-tf300tg-JB.img) then how do I root this
RBraverman said:
NOW it's there!
Okay upping to stock F/W, looking for TWRP - how do I root this
Click to expand...
Click to collapse
Flash the Android 4.2 update via fastboot: ASUS Transformer Pad TF300T Firmware: V10.6.1.27.1: http://forum.xda-developers.com/showthread.php?t=1949758
Then Flash the TWRP: http://forum.xda-developers.com/showthread.php?t=2772093
Then flash the KK rom you want in the Android Dev section, such as CM or CROM or PAC or KatKiss, etc.
cmendonc2 said:
Flash the Android 4.2 update via fastboot: ASUS Transformer Pad TF300T Firmware: V10.6.1.27.1: http://forum.xda-developers.com/showthread.php?t=1949758
Then Flash the TWRP: http://forum.xda-developers.com/showthread.php?t=2772093
Then flash the KK rom you want in the Android Dev section, such as CM or CROM or PAC or KatKiss, etc.
Click to expand...
Click to collapse
Ya know I documented the WHOLE business when I did all this the 1st and 2nd and 3rd time, especially when the system can't find the device. Now I can't find it - I have the drivers, but no docs.
************************************** edit *********************************
I need to be able to translate this so I can understand. These are the steps:
fastboot -i 0x0b05 flash blob.blob (extracted from TF300T-US_epad-10_6_1_27_1-UpdateLauncher )
fastboot -i 0x0b05 flash openrecovery-twrp-2.6.3.0-tf300tg-JB
{then root by installing root-signed.zip}?
fastboot -i 0x0b0g flash {custom ROM is desired} - Does KitKat root it?
RBraverman said:
Ya know I documented the WHOLE business when I did all this the 1st and 2nd and 3rd time, especially when the system can't find the device. Now I can't find it - I have the drivers, but no docs.
************************************** edit *********************************
I need to be able to translate this so I can understand. These are the steps:
fastboot -i 0x0b05 flash blob.blob (extracted from TF300T-US_epad-10_6_1_27_1-UpdateLauncher )
fastboot -i 0x0b05 flash openrecovery-twrp-2.6.3.0-tf300tg-JB
{then root by installing root-signed.zip}?
fastboot -i 0x0b0g flash {custom ROM is desired} - Does KitKat root it?
Click to expand...
Click to collapse
Code:
fastboot -i 0x0b05 flash blob.blob
(extracted from TF300T-US_epad-10_6_1_27_1-UpdateLauncher )
Reboot tablet.
Use this TWRP: http://d-h.st/e9H. The one you selected would have bricked the tablet.
Code:
fastboot -i 0x0b05 flash recovery [TWRP file]
Reboot Tablet.
(The custom ROM is already rooted for you with the exception of Omni ROM)
Copy ROM to SDcard, flash in TWRP to confirm it works.
I would strongly recommend using KitKat over CM10.1 because KitKat is much mroe optimized for older devices, and you should see a performance upgrade.
cmendonc2 said:
Code:
fastboot -i 0x0b05 flash blob.blob
(extracted from TF300T-US_epad-10_6_1_27_1-UpdateLauncher )
Reboot tablet.
Use this TWRP: http://d-h.st/e9H. The one you selected would have bricked the tablet.
Click to expand...
Click to collapse
That was the one I wasn't sure about - I dl'd another that I was more confident in and it turned out to be this ine - THANKS AGAIN.
cmendonc2 said:
Code:
fastboot -i 0x0b05 flash recovery [TWRP file]
Reboot Tablet.
(The custom ROM is already rooted for you with the exception of Omni ROM)
Copy ROM to SDcard, flash in TWRP to confirm it works.
I would strongly recommend using KitKat over CM10.1 because KitKat is much more optimized for older devices, and you should see a performance upgrade.
Click to expand...
Click to collapse
Which version of KitKat would the most stable?
AGAIN MANY THANKS! (as he begins to flash the stock rom)
********************************* oops ****************************
This is what I get:
C:\adb>fastboot devices
015d2994ca10140f fastboot
C:\adb>fastboot -i 0x0b05 flash blob.blob
unknown partition 'blob.blob'
error: cannot determine image filename for 'blob.blob'
C:adb>\
This with the unit ready to go, in "starting fastboot USB download protocol"
I have tried to change the name with the same result.
Am re-downloading as "I" speak.
RBraverman said:
That was the one I wasn't sure about - I dl'd another that I was more confident in and it turned out to be this ine - THANKS AGAIN.
Which version of KitKat would the most stable?
AGAIN MANY THANKS! (as he begins to flash the stock rom)
********************************* oops ****************************
This is what I get:
C:\adb>fastboot devices
015d2994ca10140f fastboot
C:\adb>fastboot -i 0x0b05 flash blob.blob
unknown partition 'blob.blob'
error: cannot determine image filename for 'blob.blob'
C:adb>\
This with the unit ready to go, in "starting fastboot USB download protocol"
I have tried to change the name with the same result.
Am re-downloading as "I" speak.
Click to expand...
Click to collapse
Use the extracted stock blob with this command:
Code:
fastboot -i 0x0b05 flash system blob.blob
cmendonc2 said:
Use the extracted stock blob with this command:
Code:
fastboot -i 0x0b05 flash system blob.blob
Click to expand...
Click to collapse
Found my notes and kept reading system blob.blob, as renaming it to system.blob - gotta get new glasses.
Waiting for the media databases to upgrade.
Flash extract img from "CUSTOM_TWRP_JB_KK_v2.7_STABLE_TF300T"? to be sure
Just rebooted, and it's 4.2.1, but everything I had - most of what I had, is still there!?! And the run?
RBraverman said:
Found my notes and kept reading system blob.blob, as renaming it to system.blob - gotta get new glasses.
Waiting for the media databases to upgrade.
Flash extract img from "CUSTOM_TWRP_JB_KK_v2.7_STABLE_TF300T"? to be sure
Click to expand...
Click to collapse
Yes the img from "CUSTOM_TWRP_JB_KK_v2.7_STABLE_TF300T" like this:
Code:
fastboot -i 0x0b05 flash recovery twrp.img
Dont forget to reboot after flashing the stock ROM and reboot after flashing twrp.
cmendonc2 said:
Yes the img from "CUSTOM_TWRP_JB_KK_v2.7_STABLE_TF300T" like this:
Code:
fastboot -i 0x0b05 flash recovery twrp.img
Dont forget to reboot after flashing the stock ROM and reboot after flashing twrp.
Click to expand...
Click to collapse
This should be the last question as the latest everything is on - no sweat really - bugged the hell out of your patience because I couldn't find my bloody notes till now.
So, the which KitKat (after a wipe) is the most stable - I've read through http://forum.xda-developers.com/showthread.php?t=2686228 and it would seem that the only obvious choice would be http://forum.xda-developers.com/showthread.php?t=2686228, but I can't/don't see the file!
RBraverman said:
This should be the last question as the latest everything is on - no sweat really - bugged the hell out of your patience because I couldn't find my bloody notes till now.
So, the which KitKat (after a wipe) is the most stable - I've read through http://forum.xda-developers.com/showthread.php?t=2686228 and it would seem that the only obvious choice would be http://forum.xda-developers.com/showthread.php?t=2686228, but I can't/don't see the file!
Click to expand...
Click to collapse
Thats the ROM I keep my tablet on during the school year, the download for the latest build is here: http://forum.xda-developers.com/devdb/project/dl/?id=7893.
cmendonc2 said:
Thats the ROM I keep my tablet on during the school year, the download for the latest build is here: http://forum.xda-developers.com/devdb/project/dl/?id=7893.
Click to expand...
Click to collapse
That's the problem - WAY too many links ... I'm downloading the one in you response but that would be the latest CM nightly - correct?
I would rather have the most stable KitKat, as you've stated that works the best with my older devices. But which is the file for the T300?
SO, CROMi-X_DEODEX_5.4_Signed.zip as DEOdexed is a bit better. Now I assume as I can't do a nanobackup I can skip that , just do a Wipe Factory from TWRP.
I can't believe how easy this was when I did 4 different tablets and 2 phones and now ... maybe I was sicker than I thought.
RBraverman said:
That's the problem - WAY too many links ... I'm downloading the one in you response but that would be the latest CM nightly - correct?
I would rather have the most stable KitKat, as you've stated that works the best with my older devices. But which is the file for the T300?
SO, CROMi-X_DEODEX_5.4_Signed.zip as DEOdexed is a bit better. Now I assume as I can't do a nanobackup I can skip that , just do a Wipe Factory from TWRP.
I can't believe how easy this was when I did 4 different tablets and 2 phones and now ... maybe I was sicker than I thought.
Click to expand...
Click to collapse
I linked you to the latest build of CROMBi-kk, the updated version of CROMi. From the ROMs I have tested, it is the most stable KitKat ROM, assuming you don't want those cutting edge features.
cmendonc2 said:
I linked you to the latest build of CROMBi-kk, the updated version of CROMi. From the ROMs I have tested, it is the most stable KitKat ROM, assuming you don't want those cutting edge features.
Click to expand...
Click to collapse
Sorry misunderstood. While I've been waiting for the ROM to dl, I noticed that my notes have fastboot xxxxxxx boot recovery.img, yet mostly what I see is fastboot xxxxxx recovery recovery.img. I also noticed that when I do a Vol/Dn/Pwr I get the 3 icons and have to select RCK to get to TWRP - I haven't noticed that mentioned anywhere - did I screw up?
To be clear - I want wipe / and "swipe to factory reset) then flash KK.
I going to try VERY hard to leave you alone now - I have taken way too much advantage of your kindness in helping me.
RBraverman said:
Sorry misunderstood. While I've been waiting for the ROM to dl, I noticed that my notes have fastboot xxxxxxx boot recovery.img, yet mostly what I see is fastboot xxxxxx recovery recovery.img. I also noticed that when I do a Vol/Dn/Pwr I get the 3 icons and have to select RCK to get to TWRP - I haven't noticed that mentioned anywhere - did I screw up?
To be clear - I want wipe / and "swipe to factory reset) then flash KK.
I going to try VERY hard to leave you alone now - I have taken way too much advantage of your kindness in helping me.
Click to expand...
Click to collapse
I'm not sure what you are talking about with "fastboot xxxxxxx boot recovery.img, yet mostly what I see is fastboot xxxxxx recovery recovery.img". As long as TWRP is working you shouldn't have to use fastboot anymore.
The new bootloader that you upgraded to only has 3 icons when you press vol-down and power. Fastboot now connects automatically if you turn on your tablet with the USB plugged in and pressing the key combo. To access TWRP, selecting RCK is the correct choice. As always, never select the Wipe Data in the bootloader menu or you will brick.
Before flashing new ROMs, you should only have to do the "swipe to factory reset" option in the TWRP recovery. If you update your ROM with a newer version of that specific ROM, you only have to Wipe Cache and Dalvik Cache.
Hey guys, I'm trying to downgrade to KitKat after all the issues Lollipop is giving me and the incompatible apps I'm trying to run.
I am following instructions here but I came across a problem when flashing the system.img file.
The error it gives me is:
FAILED (remote: Insufficient memory.)
I can't flash over system and can not boot.
What am I missing? I was rooted and my bootloader unlocked prior to starting and I tried with the factory recovery and the 1.2.1 recovery image.
Edit: My issue has been solved. Flashing the Full OTA.zip file will install KitKat over Lollipop. No need to manually flash each file through fastboot. I wish guides would tell you that instead.
BlackDave said:
Hey guys, I'm trying to downgrade to KitKat after all the issues Lollipop is giving me and the incompatible apps I'm trying to run.
I am following instructions here but I came across a problem when flashing the system.img file.
The error it gives me is:
FAILED (remote: Insufficient memory.)
I can't flash over system and can not boot.
What am I missing? I was rooted and my bootloader unlocked prior to starting and I tried with the factory recovery and the 1.2.1 recovery image.
Click to expand...
Click to collapse
I don't know why that wouldn't work. Have you tried just downloading the image from nvidia HERE?
I'm assuming wifi since your sig says 16GB
Keithn said:
I don't know why that wouldn't work. Have you tried just downloading the image from nvidia HERE?
I'm assuming wifi since your sig says 16GB
Click to expand...
Click to collapse
Those are the same files as the ones I downloaded in the other thread.
I got my tablet working again on Lollipop 5.0.1 but that's not where I want to be. I've searched about my error message but most threads I found went unanswered.
Your best bet might just be to try getting a full OTA and flashing it through cwm or something. I'll try with mine when I have some time to backup and flash, probably later tomorrow. If I find anything out I'll post.
Sent from my SHIELD Tablet
BlackDave said:
I got my tablet working again on Lollipop 5.0.1 but that's not where I want to be. I've searched about my error message but most threads I found went unanswered.
Click to expand...
Click to collapse
I just flashed the images and booted.
Did you accidentally try flashing to the wrong place, such as flashing to boot( which would be too small) instead of system? Did you do all of the commands yourself or use the .bat? My shield disconnected after doing the boot.img and system.img for some reason, so I had to select fastboot protocol to reboot the bootloader and continue to flash the userdata.img, blob, and battery.dtb.
was your tablet internal memory full?, try wipping data and chace and you could use the script that the original Nvidia recovery image has zipped. I went up and down like 3 times, im in kitkat right now and not experiencing any problem.
Iams1002 said:
was your tablet internal memory full?, try wipping data and chace and you could use the script that the original Nvidia recovery image has zipped. I went up and down like 3 times, im in kitkat right now and not experiencing any problem.
Click to expand...
Click to collapse
No I wipped internal data since I keep everything on external and it still didn't work.
Keithn said:
I just flashed the images and booted.
Did you accidentally try flashing to the wrong place, such as flashing to boot( which would be too small) instead of system? Did you do all of the commands yourself or use the .bat? My shield disconnected after doing the boot.img and system.img for some reason, so I had to select fastboot protocol to reboot the bootloader and continue to flash the userdata.img, blob, and battery.dtb.
Click to expand...
Click to collapse
So I should just flash the ota.zip?
Also i did everything like the guide. I flashed boot to boot, recovery to recovery. The only thing that gave me an error was system. Userdata, blob, and battery also flashed successfully. After that didn't work, I also tried the .bat and that didn't work either. Flashing the 5.0.1 update got my tablet running again.
BlackDave said:
No I wipped internal data since I keep everything on external and it still didn't work.
So I should just flash the ota.zip?
Also i did everything like the guide. I flashed boot to boot, recovery to recovery. The only thing that gave me an error was system. Userdata, blob, and battery also flashed successfully. After that didn't work, I also tried the .bat and that didn't work either. Flashing the 5.0.1 update got my tablet running again.
Click to expand...
Click to collapse
If you can find a full ota.zip for update 1.2.1 I'd try that. I'm not sure why you would be having this issue. The only other things I can say to try is redownloading and rebooting the boot loader (select fastboot protocol) between images in case something funny is happening there. Let us know how you end up doing.
Sent from my HTC M8
Keithn said:
If you can find a full ota.zip for update 1.2.1 I'd try that. I'm not sure why you would be having this issue. The only other things I can say to try is redownloading and rebooting the boot loader (select fastboot protocol) between images in case something funny is happening there. Let us know how you end up doing.
Sent from my HTC M8
Click to expand...
Click to collapse
I flashed the 1.2.1 OTA update and it worked. The first time I tried, I did using the TWRP recovery but for some reason, that recovery fails to flash OTAs, so I went with CWM and flashed the 2.1 update and all worked again. After a while, I got tired of all the issues lollipop gave me so that's why I tried following that guide to downgrade.
In the end, using CWM and flashing the OTA is the best way to go. Thank you all for you help.
DISCLAIMER: I AM NOT LIABLE TO ANY DAMAGE THAT HAPPENS TO YOUR DEVICE BECAUSE OF DOING ANYTHING WRONG.
MOTO G4 PLUS [XT1643]
This is for those who had flashed a custom kernel on their stock ROM and now want to revert to stock.
REQUIREMENTS:
1. TWRP 3.0.3-n2 by @Shreps .
https://forum.xda-developers.com/mo...covery-twrp-3-0-2-r3-moto-g4-g4-plus-t3494337
This one is more updated/maintained than the official 3.0.2 version.
2. 7Zip Compression Utility:
Download and install on your PC. I use this as it gives the maximum ultra level compression. See Downloads below.
PROCEDURE:
1. Download and extract the TWRP.7z using 7Zip.
2. Place the TWRP folder it in the root directory of your INTERNAL STORAGE.
2. Just reboot TWRP once and choose Restore and then choose this: athene_93-14_boot
3. Swipe to restore.
NOTE: As a general recommendation for all zip installations and backup/restore using twrp, Wipe Cache and ART Cache before you Reboot to System.
4. You're DONE
DOWNLOADS:
Google Drive Link for the file:
https://drive.google.com/open?id=0B25DpDahxm52MDlBRlVqNElkaUE
7-ZIP Download Link:
http://www.7-zip.org/download.html
IF YOU WANT ENTIRE STOCK ROM ( TWRP BACKUP) VISIT THIS THREAD BY @Greekgodmerwyn .
https://forum.xda-developers.com/moto-g4-plus/how-to/android-7-0-moto-g4-plus-npj25-93-14-t3544601
HIT LIKE IF I HELPED YOU! :fingers-crossed: :good:
Hey I need the file bit it is in bin so give a alternative link
Can i install this to xt1644 retus?
Dont know bro I just want the 1643 one
dedik46 said:
Can i install this to xt1644 retus?
Click to expand...
Click to collapse
Not tried. Make additional backups and try. :good:
https://drive.google.com/open?id=0B25DpDahxm52MDlBRlVqNElkaUE
Not Found
Error 404
Please re-upload.
nextheart said:
https://drive.google.com/open?id=0B25DpDahxm52MDlBRlVqNElkaUE
Not Found
Error 404
Please re-upload.
Click to expand...
Click to collapse
Oh wait. Try this, @nextheart
https://www.androidfilehost.com/?fid=745425885120722570
@tywinlannister7 Thanks for quick reply.
As far as I can understand, this file should be flashed (restored) after restoring my TWRP back up of nougat stock rom taken in January-2017. Currently I am on RR-MM.
Shall I able to take OTA then?
nextheart said:
@tywinlannister7 Thanks for quick reply.
As far as I can understand, this file should be flashed (restored) after restoring my TWRP back up of nougat stock rom taken in January-2017. Currently I am on RR-MM.
Shall I able to take OTA then?
Click to expand...
Click to collapse
For OTA updates to work, you'd need a stock recovery on your device too; TWRP is a no go. Once you've restored your TWRP backup of your Nougat stock ROM (which hopefully may have the stock boot still), you can flash the stock recovery linked here https://forum.xda-developers.com/moto-g4-plus/how-to/how-to-ota-rooting-nougat-npj-25-93-14-t3601747
I imagine the easiest option is to flash the recovery in fastboot (same as you did with TWRP) using 'fastboot flash recovery recovery.img', then rebooting into recovery.
I think, though I've not tried it with a stock recovery, that you should be able to flash the recovery image in TWRP:
tap Install in the TWRP menu
Select 'install image's
Find your stock recovery image and select
Choose recovery as the image type
Flash and reboot to recovery.
Then, provided your system has a stock kernel, no modifications to your system and a stock recovery (bootloader doesn't matter), you should be able to update via OTA.
@echo92 Thanks for detailed guide.
I had flashed SuperSU on Nougat stock ROM, so stock boot might be affected. Am I right?
In short, I want to sell the device, so I want to return to stock.
nextheart said:
@echo92 Thanks for detailed guide.
I had flashed SuperSU on Nougat stock ROM, so stock boot might be affected. Am I right?
In short, I want to sell the device, so I want to return to stock.
Click to expand...
Click to collapse
You could have directly flashed the latest March 1 Security firmware via fastboot and lock your bootloader too.
tywinlannister7 said:
You could have directly flashed the latest March 1 Security firmware via fastboot and lock your bootloader too.
Click to expand...
Click to collapse
Thank you for pointing out.
Will I lose my IMEI or WIFI MAK or any thing else by fastboot method? Because I have read that some users are losing such things by fastboot method.
nextheart said:
Thank you for pointing out.
Will I lose my IMEI or WIFI MAK or any thing else by fastboot method? Because I have read that some users are losing such things by fastboot method.
Click to expand...
Click to collapse
Shouldn't create any such issues. Anyways, you can make an entire backup of the fsg and other partitions in twrp.
Yes, your data will be wiped though.