{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You are looking for a special modded Clockworkmod recovery?
Clockworkmod Recovery v4.0.0.5
removed downloadlinks cause of issues with the new unity kernel.
please use this very special recovery
Just have a look on this site: 4EXTRecovery v1.1.1 | STAY @EXT4 | Convert EXT4 without losing data | Advanced Backup
Clockworkmod Recovery v3.2.0.0
downloadlink:
PG88IMG-RECOVERYIMG-3.2.0.0.zip
Clockworkmod Recovery v3.1.0.1
downloadlink:
PG88IMG-RECOVERYIMG-3.1.0.1.zip
or visit my blog dev page: lbc mod android development - custom recovery
Install Instructions:
download the zip package
rename it to PG88IMG.zip
put that file on the root of your sd card
start you phone in bootloader (hboot not fastboot)
the bootloader will ask you if you want to install recovery.img
confrim
reboot
rename the file again into something else (cause bootloader will always try to flash if a PG88IMG.zip file is on your sd card
loveboatcaptain said:
Hey Guys,
just have the first booting version of ClockworkMod Recovery v.3.0.2.4 on my phone.
View attachment 575564
a full working beta will come in the next days.
Install instructions will follow, too.
CREDITS: this is basicly the work of HCDR.Jacob how helped my to build this, cause my macbook sucked at building from source. so give him a big tanks too ;-)
see you later with a download for everyone with s-off
regards
Click to expand...
Click to collapse
woohoo
you are great
Ah mr mac user succeeded gratz
Sent from my HTC Incredible S using XDA Premium App
Hawkysoft said:
Ah mr mac user succeeded gratz
Click to expand...
Click to collapse
Yeah, with a little help from my friends ;-)
Jacob is fixing the last bugs and than i think were done and can do some tests before release.
regards
Maybe ours work for you to, koush made ours public today. Ill give u the info tomorrow, should be all the same
Sent from my HTC Incredible S using XDA Premium App
the beta tests have finished...
we talked to koush and he put it into ROM MANAGER just in this minute...
so happy flashing for all with s-off and root.
regards
p.s. don´t forget to thank HCDR.Jacob. He build it together and fixed the bugs and of course koush for pushing it so quick to ROM MANAGER.
thx to this great community
loveboatcaptain said:
Hey Guys,
[ROMmanager]
regards
Click to expand...
Click to collapse
Cool - working, thanks!
running backup now - so let the de-sense begin - I always brake some things when playing around to strip sense, so great to have full backup...
dont know said:
Cool - working, thanks!
running backup now - so let the de-sense begin - I always brake some things when playing around to strip sense, so great to have full backup...
Click to expand...
Click to collapse
feel free to test my first rom ;-)
this would be easier to "de-sense" cause it´s allready deodexed. so you needn´t delete so much stuff ;-)
a light version will follow the nexts days, which will be "de-sensed" and have a custom launcher like ADW or LP
regards
loveboatcaptain said:
feel free to test my first rom ;-)
this would be easier to "de-sense" cause it´s allready deodexed. so you needn´t delete so much stuff ;-)
a light version will follow the nexts days, which will be "de-sensed" and have a custom launcher like ADW or LP
regards
Click to expand...
Click to collapse
It's a very light desense I want (only get rid of the ad-ware inkluded and some others like twitter..)
I'm on ADW because of the cool themes available.
THANKS for the possibility of real rooting (unsecure and clockwork) again..
Hi, how can I root my desire s save
Sent from my Desire S using XDA Premium App
M0ng0 said:
Hi, how can I root my desire s save
Sent from my Desire S using XDA Premium App
Click to expand...
Click to collapse
Hey, today i unlocked mine with an xtc clip.
Then I flashed the unsecured Boot Image. I hope it is called so .
After that worked successful, i rooted it with SuperOneKlick.
Maybe this works for you too.
Any chance you can get in touch with the developer of this as there seems to be a very annoying bug.
Everytime i include:
format CACHE or
format("ext4", "EMMC", "/dev/block/mmcblk0p27", "/cache");
the recovery will not flash the ZIP. It will always give a STATUS 1 error.
So i have to manually format cache and run my ZIPS.
Thanks.
anybody successfully tried to revert on stock recovery?
fastboot says "FAILED (remote: not allowed)", and with cwm recovery it's impossible to try new OTA...
MarylandCookie said:
Any chance you can get in touch with the developer of this as there seems to be a very annoying bug.
Everytime i include:
format CACHE or
format("ext4", "EMMC", "/dev/block/mmcblk0p27", "/cache");
the recovery will not flash the ZIP. It will always give a STATUS 1 error.
So i have to manually format cache and run my ZIPS.
Thanks.
Click to expand...
Click to collapse
hey dude,
i ported the recovery together with a friend. so i´m your man ;-)
i never noticed that there is a problem with formating cache partition, cause i don´t touch it with my updater-script.
so first question:
why you will add that to your updater-script? me for myself prefere the way of wiping my phone manually. and that works very well with CMR. i also tested it in the mount/partition menu.
i would not like it, when a script wipes stuff and i did not know about.
i only use format for system in my full update.zip´s. in updates for my rom i did not wipe anything.
second question: did you know that cache partition is always mounted when recovery starts? perhaps thats the problem.
regards
mih_ said:
anybody successfully tried to revert on stock recovery?
fastboot says "FAILED (remote: not allowed)", and with cwm recovery it's impossible to try new OTA...
Click to expand...
Click to collapse
those fastboot commands only works with an ENG S-Off bootloader. which we dont have. we have SHIP S-Off... there are differences between those both.
our bootloader can everything the ENG can with fastboot commands. we have to use a zip file to flash things like recovery or splash.
you have to add your recovery backup img into my PG88IMG-unsecured_bootimg.zip file from this post [BOOT] Root for S-Off with unsecured Boot Image rename it to PG88IMG.zip and add your recovery.img into that zip file and remove the boot.img file.
than put the file on the root of your sdcard and reboot into bootloader.
the file will be flashed automaticly.
after reboot your phone, rename the file again to something else, cause every time you are in bootloader and this file is named PG88IMG.zip on your sdcard thhe bootloader will try to flash it.
just a little tipp at the end: you can add every img file into this zip. system and data img files from nandroid backups are working too ;-)
regards
Thank you!
I'll try it next time, i'll need it
But i've managed to flash it through flash_image from this link:
http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#HBOOT_partition_map
with recover.img from OTA downloaded.
After OTA i've lost the root, but gingerbreak still works...
mih_ said:
Thank you!
I'll try it next time, i'll need it
But i've managed to flash it through flash_image from this link:
http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#HBOOT_partition_map
with recover.img from OTA downloaded.
After OTA i've lost the root, but gingerbreak still works...
Click to expand...
Click to collapse
Could you PLEASE give me a short (or long ) description how to install the ota?
No idea what to do with the linked code...
EDIT Extracted the boot.img from ota and copoed it to PG88IMG.zip - restart - run ota-update -> fail
EDIT2 I'm an idiot: instead of boot.img it is a great idea to try it with recovery.img *LOL*
You just have to replace clockworkmod ecovery with stock one.
I've taken it from OTA downloaded.
It contains file firmware.zip inside, which contains recovery.img as well.
You can flash it with tool flash_image (http://www.thinkthinkdo.com/trac/project1/raw-attachment/wiki/vision_utilities/flash_image.zip)
Just put it somewhere to device, where you can run it (for instance/data/local/bin/, /system/bin/ if remounted to rw, /sdcard if remounted to exec)
and run from device or adb shell like%
su
flash_image recovery /sdcard/recovery.img
after that, you can reboot to hboot, check out that you do not have cwm recovery anymore, boot to android and install OTA as usual from menu...
does the recovery also do a backup of the radio?
(my wifi is broken sinve ota update - and I'm an stock recovery now, so can't test at the moment)
Cache being mounted or unmounted isnt the issue.
I can wipe cache manually but automatting it in the script seems the break the whole process.
Its good for testing and having a fresh install.
Lets android re-build everything.
Take from Clockworks How to:
wipe cache partition
Wipes the cache partition of the device to clear all the data accumulated there over use. This is often used before installing a new ROM, app, kernel or any similar mod via recovery
Click to expand...
Click to collapse
http://www.addictivetips.com/mobile...-and-how-to-use-it-on-android-complete-guide/
Related
hello.i open this thread to show you how to solve a2sd not working on custom roms so you people can use your favorite rom with all the features and rom developers can continue developing of their rom and make them more and more better.
First of all the reason why a2sd dont work and ext partition doesnt mount:
for these feautures and others that dev gives as with his rom,the kernel ramdisk is modified (by xda kitchen or "by hand").so if this boot.img is not flashed into your phone,those feautures wont work.every custom rom have her boot.img into the flashable rom.zip.the thing that our rom creators and devs dont know(cause all phones are not the same) is that the boot.img in the zip doesn flash!.our phone cant flash boot.img from recovery and the reason is because in this phone kernel and recovery are in the same partition and not separately partition like most phones.
The solution:
REMEMBER THAT YOU DO IT WITH YOUR OWN RISK!
its just very simple:the only thing you have to do is to flash the boot.img that comes with your rom and the only way to do that succesfull is with Odin.(this ofcourse will give the custom bin counter 1 up because its a modified and not stock kernel).also have in mind that you have to flash it once.if for any reason you want to reflash your rom,you just do wipe data etc and reflashing the rom.zip.its not necesary to reflash the kernel(boot.img) again.its still there and will only change if you flash another boot.img or stock firmware with Odin.
So i will give two options.
1.download my PDA_S5360_kernel.tar from TermaRomGR threadhttp://forum.xda-developers.com/showthread.php?t=1520167(the mods in all of these kernel are about the same).flash it with Odin in pda field (first try without wipe anything or reflashing stock firmware first.just boot in download mode,flash with odin and reboot,it should work ok.DONT FORGET TO BACKUP YOUR ROM FIRST!JUST IN CASE!).reboot may take more time dont worry.when phone is on your ext partition should be mounted.you can try with terminal simulator:
su
a2sd check
if everything is ok you can remove your dalvik cache to your sd if you want for more internal memory free space:
su
a2sd cachesd
the phone will reboot.it will late to reopen just be patient and then your internal memory will be almost empty.but have in mind that this partition is not as fast asthe internal memory so some apps or games maybe slow a bit.
2.the other option is to flash the kernel(boot.img) that come with your custom rom.how to do that (thanks to Doky):
copy the boot.img that is inside the zip of the rom you are using.
download my PDA_S5360_kernel.tar
find in web the program total commander for windows
open t commander and in left window navigate to my PDA_S5360_kernel.tar file and get into it.in the right window find the boot.img of your rom.drag it and drop it to the left window so it replace the boot.img into the .tar file with yours.its ready.just flash it with Odin.
Some important things too that i notice from my experiments:
with busybox 1.18 your rom will not boot after nove dalvik cache to sd
it will work nice with 1.17 but its not suitable for people who want to run v6 script.for those who want to run v6 you must download busybox instaler from market and install v1.19.2.if after that you have problems with wifi try another version (1.19.3 or 1.19.4).and report back what works ok and what not so all people together can find the best setup.
Please tell to the devs of your roms to read this thread so they learn about the solution to this problem so they can create even better and better roms
I love you. I'll try this tomorrow.
Sent from my GT-S5360 using xda premium
Why do i have SD Card Remove Problem then when i boot back i was in the Welcome Screen where my info of google account is being ask. I skipped it then check the settings, my account was just there still. Also having this Turning off by itself problems. This was just started when i begin using a2sd supported ROMS. But when i'm just on stock or non-a2sd roms it work fine. Maybe its the boot.img?
eyjay1991 said:
Why do i have SD Card Remove Problem then when i boot back i was in the Welcome Screen where my info of google account is being ask. I skipped it then check the settings, my account was just there still. Also having this Turning off by itself problems. This was just started when i begin using a2sd supported ROMS. But when i'm just on stock or non-a2sd roms it work fine. Maybe its the boot.img?
Click to expand...
Click to collapse
which boot.img you instal?mine?i dont think that this is the problem.for me and for others works ok.try wipe cache and if the same try wipe data/reset.
Thank you for the info bro!
Sent from my GT-S5360 using xda premium
bumslayer said:
I am interested to know what is so special about your boot.img and how you customized it. I am guessing you decompiled a stock boot.img to come up with your own
Sent from my GT-S5360 using xda premium
Click to expand...
Click to collapse
with xda kitchen.it doesnt has something xterme only a2sd, init.d support and ext mount on boot.
So this will happen?
before flashing ur 5360kernel.tar
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
after flashing
is this correct?
ronnieryan said:
So this will happen?
before flashing ur 5360kernel.tar
after flashing
View attachment 926853
is this correct?
Click to expand...
Click to collapse
yes its succesfuly flashed and should working right
termagazis said:
with xda kitchen.it doesnt has something xterme only a2sd, init.d support and ext mount on boot.
Click to expand...
Click to collapse
Oh, so I can take a stock firmware from Doky73's thread and modify it thru xda kitchen and change the kernel to include just init.d support (I kind of hate a2sd at the moment)? What about ext4 file system support? Is this possible?
By xda kitchen you mean the one by dsixda, right?
just like to ask if a2sd's low memory setting would conflict with [email protected] scripts?
coz after installing a2sd in my phone with [email protected] script, i sometimes notice that memory usage would reach 240+?
bumslayer said:
Oh, so I can take a stock firmware from Doky73's thread and modify it thru xda kitchen and change the kernel to include just init.d support (I kind of hate a2sd at the moment)? What about ext4 file system support? Is this possible?
By xda kitchen you mean the one by dsixda, right?
Click to expand...
Click to collapse
dont know.just try it if you want.for ext4 suport we need a custom kernel that will suport that
ronnieryan said:
just like to ask if a2sd's low memory setting would conflict with [email protected] scripts?
coz after installing a2sd in my phone with [email protected] script, i sometimes notice that memory usage would reach 240+?
Click to expand...
Click to collapse
maybe they conflict.use one of them
I'm using hybrid2.1 ,
Qus 1: is it necessary to partition SD card if I wanna enable a2SD? If yes then when&how?
Qus 2: is the1St option stated above mint to flash only the tar file by Odin and other fields of Odin remain empty?
And please give a link to download Odin & a link for step by step tutorial on connecting to Odin(with phone preparation ).
Sent from my GT-S5360
a.m.muammar said:
I'm using hybrid2.1 ,
Qus 1: is it necessary to partition SD card if I wanna enable a2SD? If yes then when&how?
Qus 2: is the1St option stated above mint to flash only the tar file by Odin and other fields of Odin remain empty?
And please give a link to download Odin & a link for step by step tutorial on connecting to Odin(with phone preparation ).
Sent from my GT-S5360
Click to expand...
Click to collapse
1.yes its necesary to have an ext2 or ext3 partition.you can create it with skin1980 CWM recovery in advance/partition sdcard.a partition 500Mb is enough.(before do it backup everything from your sdcard to your pc because this procedure will erase everything in your sdcard.)
2.for Odin google it Odin3-v1.85.Here is how to do it:
1. you put my tar in pda field and the other remain empty(check only "Auto reboot" and "F.reset time")
2. Now turn off your Samsung Galaxy Y (just for make sure is completely off, remove the battery for a few sec and put that back)
3. Press Volume[-] + Home + Power to boot in Download Mode
4. Hold the buttons until a warning screen with choise show up.
5. Select Continue (Volume[+]), then it`s go to download mode
6. Connect the cellphone (via USB cable) to PC, wait until ODIN detect the device.
7. Click Start
8. Wait until ODIN give feedback respon PASS
it`s mean the flashing proccess is complete. Samsung Galaxy Y will auto reboot.
9. unplug the USB cable from PC/Laptop
Thanks bro, I have 2 questions more,
before flash your PDA is it necessary to go back to stock rom?
Currently I'm using V6 with busy box v1.18 on hybrid2.1, should I change it to v1.19.2?
Your link for v1.19.2 in terma rom thread is not working.
Sent from my GT-S5360
a.m.muammar said:
Thanks bro, I have 2 questions more,
before flash your PDA is it necessary to go back to stock rom?
Currently I'm using V6 with busy box v1.18 on hybrid2.1, should I change it to v1.19.2?
Your link for v1.19.2 in terma rom thread is not working.
Sent from my GT-S5360
Click to expand...
Click to collapse
its not necesary.flash it as it is.just dont forget wipe data and wipe cache.for busybox 1.19.2 just download from market
termagazis said:
its not necesary.flash it as it is.just dont forget wipe data and wipe cache.for busybox 1.19.2 just download from market
Click to expand...
Click to collapse
After which step I should wipe data and cache bro?
Sent from my GT-S5360
a.m.muammar said:
After which step I should wipe data and cache bro?
Sent from my GT-S5360
Click to expand...
Click to collapse
before flashing the rom zip
termagazis said:
before flashing the rom zip
Click to expand...
Click to collapse
You mint after flashing .tar file I have to reflash my hybrid rom?
Sent from my GT-S5360
a.m.muammar said:
You mint after flashing .tar file I have to reflash my hybrid rom?
Sent from my GT-S5360
Click to expand...
Click to collapse
**** i messed up!sorry.you just flashing pda file and reboot and install busybox.no wipe
Hello, Infusers...im back and ive brought with me TeamWin Recovery Project! Official TWRP website: http://www.teamw.in/project/twrp2
What is this?
-Its an alternitive to CWM recovery
What are the advantages?
-Full touch screen interface
-Built in file manager
-keyboard (gives you the ability to name your backups...or rename other files from with in recovery)
-clock
-battery percentage
-swipe to confirm flashes/wipes (no more of the "no no no no yes no no"
-themeable!!!
-and more!!!
***DOES NOT WORK WITH MTD JELLYBEAN...yet***
Unfortunatly our recovery is built into the boot.img after flashing any ics rom you will lose the twrp recovery and get cwm recovery again...just tick the box to re-inject twrp before sliding to confirm your flash...or go to advance options and click on re-inject twrp
Download:
TWRP
Flashing Instructions (does not effect your current set up/kernel...only replaces CWM)
1) boot into recovery
2) flash zip
3) reboot
4) next time you go to recovery you will have TWRP
5) Flash this zip after every new rom flash to keep TWRP
***important for updating***
-if updating twrp from a previous build make sure you disable "re-inject twrp after flash" if you dont it will reinject the old twrp
-If coming from gingerbread you have to boot into your ics or jb Rom before being able to flash the zip...after that you can flash after every Rom flash
how does the zip work? i thought it was built into the boot.img?
Credit goes to smasher816 for this..he made an install script that takes your boot.img of your rom, then takes the recovery ( ramdisk-recovery.img) and injects it into your current boot.img...leaving the actual kernel untouched!
Satandard Disclaimer
Use this recovery at your own risk!!! im not responsible for anything that happens to you, your phone, your friends, your family, or anything but i will do my best to resolve any and all problems you may encounter
Thanks/Credit:
TeamWin-Recovery/source/compiling instructions
Entropy-CM9/kernel/guide for compiling/source
JT-for getting us ics in the first place
JScott30-sold me his infuse which allowed for me to do this
Smasher816-your install script has allowed for an easy recovery flash
Did i miss anyone? -let me know...dont want to leave any one out
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
the above screen shots were taking from http://www.teamw.in/project/twrp2
the below screenshots are pictures taken of my infuse with it in action
And...video of it in action
http://www.youtube.com/watch?v=7gJ7idj8y0g&feature=plcp
TWRP-2.2.1.4 8-6-12
-fixed aroma
-should be completly bug free
TWRP 2.2.1 6-8-12
-updated to twrp 2.2.1.4
-fixed backups
TWRP 2.2.1 8-3-12
-Added the abilty to reinject twrp through an option under the advanced menu...use that option or reflash zip
TWRP 2.2.1 sdfix
-Fixed sdcard error
-fixed install script so you no longer have to mount system in mounts instorage...just flash the zip and it will mount for you
8-2-12
-initial release
Things to do...
1) Figure out if its possible to compile the recovery and flash it with out messing with a user's kernel/current set up
-solved...op has been updated with fix
2) fix the sdcard error
-solved...op has been updated with fix
3) fix backup problem (cant create a backup)...currently the only known bug
-solved fix uploaded to goo.im
4) make a CWM recovery zip for people who want to go back to CWM
-done, added as an atachment to the op
5) fix the aroma bug...
-fixed...uploaded to goo.im
6) Keep this up to date with official twrp source
-on going process...ill check every other day for updates to the source
TWRP THEMES
You can find some themes for twrp here: TWRP 2.X Themes
-keep in mind that themes can introduce bugs...so use them at your own risk...if your intrested in creating your own them check out this: http://teamw.in/project/twrp2themers
-themes must go in this directory /sdcard/TWRP/theme/ and it must be named ui.zip -reboot to recovery and it will be applied...thats right just reboot no need to flash!
My TWRP Themes -hosted on goo.im (soon to be featuring every color of the rainbow...and then some)
Inverted theme! by supernewbdev
First....
Very nice bro..this is awesome no more vol up+down button and power when flashing roms when your are in recovery mode and all fully touch screen...good job sir
Nice man always great to have options!
Sent from my SGH-I997 using xda app-developers app
I have been wanting to try twrp in my infuse since I tried it on my transformer.
This is a great addition to our community, Thanks for bringing it! :victory:
Edit: I presume it still not compatible with JB, am i right?
andros11 said:
I have been wanting to try twrp in my infuse since I tried it on my transformer.
This is a great addition to our community, Thanks for bringing it! :victory:
Edit: I presume it still not compatible with JB, am i right?
Click to expand...
Click to collapse
At the moment no...its built into the ics boot.img -so flashing this would give you an ics kernel
Not sure when and if ill be able to bring it to JB...will have to wait for TeamWin to update it for JB
EDIT: i think i know how to let people use this without messing with there current kernel/set up...gotta test the theory first
Edit #2...theory correct...no more will you have to flash the boot.img or CM9 to get TWRP...OP will be updated shortly with details
Omg. Mg this is awesome downloading as of now
Edit: can the boot.img be flashed with sgs kernel flasher?
Edit#2: saw the zip flashed it and it works like a charm.
Sent from my AOKP'd Infuse 4G
OP updated...just download the zip and flash it-next time you boot to recovery you will have TWRP...just make sure you mount system before flashing...
EDIT: if my other theory is correct...this may now be compatible with JB...gonna download cm10 now and test the zip with it...will report back later
isaiahe97 said:
Omg. Mg this is awesome downloading as of now
Edit: can the boot.img be flashed with sgs kernel flasher?
Sent from my AOKP'd Infuse 4G
Click to expand...
Click to collapse
not sure...but you can download the zip and flash that instead in recovery...it will not mess with your rom or kernel
works with jellybean...just mount system and flash the zip...
Recovery updated...fixed the sdcard error, as well as edited the updater script to mount system...in other words you dont have to mount system in "mounts and storage" anymore just download and flash
currently only known bug at the moment is not being able to create a backup...im looking into it
EDIT: Just found out there's a way to enable the recovery to auto insert itself after every Rom flash...currently working on it...if it works then one flash and you will have it for good! It will be added to the advanced settings I believe...so you can enable the auto insert or disable it if you wanna go back to old cwm...
EDIT 2: alright...misread...it doesnt auto insert :/ but still useful tho heres what it does: after flashing a rom instead of flashing the recovery zip again you go to advanced options, in there on the bottom right corner you will see the option to "re-inject TWRP" it essentially does the same thing as the zip...so if you delete the zip or dont wanna flash the recovery zip ever again just use that option after every rom fash and it will inject the recovery into the rom
ill include the re-inject option in the next update (when i figure out and fix the backup problem...) unless you guys want that now...just dont wanna do a bunch of tiny updates in one day lol...i feel like that would be annoying for you guys
Been getting tired of CWM so i am gonna have to try this out. Thks:cyclops::good:
BTW. Doesn't the face plate on the Otterbox case mess with infared sensor in detecting during calls.
I got a Ballastic case the other day and i couldn't seem to hang up a damn phone call after rebooting
---------- Post added at 11:21 PM ---------- Previous post was at 11:09 PM ----------
mg2195 said:
OP updated...just download the zip and flash it-next time you boot to recovery you will have TWRP...just make sure you mount system before flashing...
EDIT: if my other theory is correct...this may now be compatible with JB...gonna download cm10 now and test the zip with it...will report back later
Click to expand...
Click to collapse
Might wanna edit the OP.....
1) boot into recovery
2) Mount system (mounts and storage > mount /system)
3) flash zip
4) reboot
5) next time you go to recovery you will have TWRP
6) Flash this zip after every new rom flash to keep TWRP
Click to expand...
Click to collapse
slicingtaco said:
Been getting tired of CWM so i am gonna have to try this out. Thks:cyclops::good:
BTW. Doesn't the face plate on the Otterbox case mess with infared sensor in detecting during calls.
I got a Ballastic case the other day and i couldn't seem to hang up a damn phone call after rebooting
---------- Post added at 11:21 PM ---------- Previous post was at 11:09 PM ----------
Might wanna edit the OP.....
Click to expand...
Click to collapse
I fixed it so that when you flash it you no longer need to mount system...if you have the twrp 2.2.1 sdfix then you no longer need to mount system (I added the command in the updater script to.mount it)
Sooooo...just download, flash and enjoy...
Anyways...two days of non stop compiling...and I'm only doing recovery...don't know how the guys (Scott) at the CM10 thread do it...I'm pooped, time for bed
Also I don't use my infuse as my DD...so I don't have a sim in it...I use it for development only...my vivid is my DD
Sent from my HTC Holiday using Tapatalk 2
first of all, coolioso ! second, thanks! third, ok so to make sure, do I flash a rom, then reboot into recovery, then flash this alter-recovery, or can I just flash it along with the rom and the gapps ect.?
I'm loving this MG, This looks and feel so good. Thanks
Sent from my SGH-I997 using Tapatalk 2
Excellent work. Thank you.
megazeroxuxm said:
first of all, coolioso ! second, thanks! third, ok so to make sure, do I flash a rom, then reboot into recovery, then flash this alter-recovery, or can I just flash it along with the rom and the gapps ect.?
Click to expand...
Click to collapse
You can flash this and reboot into recovery
You can flash it after a Rom flash
You can flash it anytime...but if you flash a Rom make sure you flash this again
Sent from my HTC Holiday using Tapatalk 2
Back up will be great. I know you are working on that issue.
Also, will this only work with the Samsung Infuse 4G.
This is a flashable ZIP, containing the latest kernel and build of Android 4.3 by Google. It is made for the Google Nexus 7 3G, and is flashable through TWRP. I did not test it since I don't have a 3G model of the Nexus 7.
Download link: https://mega.co.nz/#!xskHxaRb!ZP3kYCk66VinJc70TswVBSAv8yZ3QoKKgUCtzVe66lY
Odexed, and no superuser management tool. Chainfire released an experimental version supporting Android 4.3 on his Google+. so I'll add that to the OP later.
Enjoy!
Anybody tested?
Also, will there be radio and bootlosder in flashable form?
Fatal1ty_18_RUS said:
Anybody tested?
Also, will there be radio and bootlosder in flashable form?
Click to expand...
Click to collapse
From what i can see, there is no bootloader and radio in it, so anyone has to flash it by himself.
EDIT: The ZIP works fine, i just flashed bootloader and radio through fastboot prior to installing it over TWRP. Haven't tested any root zips, yet.
i got 4.3
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Root does work, flashing this zip. Although Titanium Backup didn't work at first, i installed busybox, changed the backups location from /storage/emulated/0 -> /storage/emulated/legacy and i had to uncheck the first backup to make the restore work (no idea which of those three things actually did the work).
biggoldring said:
Click to expand...
Click to collapse
That's great, but can someone explain why baseband is still old (i've flashed 0.18 and on fastboot i see the correct version, but on System->About i get still 0.17)?
stadicon said:
Root does work, flashing this zip. Although Titanium Backup didn't work at first, i installed busybox, changed the backups location from /storage/emulated/0 -> /storage/emulated/legacy and i had to uncheck the first backup to make the restore work (no idea which of those three things actually did the work).
That's great, but can someone explain why baseband is still old (i've flashed 0.18 and on fastboot i see the correct version, but on System->About i get still 0.17)?
Click to expand...
Click to collapse
you mean you flash the zip in stock recovery??
Gabrieltan said:
you mean you flash the zip in stock recovery??
Click to expand...
Click to collapse
I don't have stock recovery, TWRP remained untouched through this process. I just installed this zip to gain root access through TWRP, then changed setting in Titanium Backup to make it work..
stadicon said:
I don't have stock recovery, TWRP remained untouched through this process. I just installed this zip to gain root access through TWRP, then changed setting in Titanium Backup to make it work..
Click to expand...
Click to collapse
so your point is flash the rom then direct flash the zip?? because if boot then flash the zip definitely TWRP will lose. Am i right?
Gabrieltan said:
so your point is flash the rom then direct flash the zip?? because if boot then flash the zip definitely TWRP will lose. Am i right?
Click to expand...
Click to collapse
No, why it should get lost?
The process i did was:
1) Boot at bootloader ([POWER]+[VOL-])
2) fastboot flash bootloader <bootloader.img>
3) fastboot flash radio <radio.img>
4) Start recovery (TWRP)
5) Flash stock-4.3 zip
6) Flash SuperSU zip
That's all. Neither recovery, nor userdata were touched through this process. The only affected partitions are bootloader, radio, system, boot and data.
stadicon said:
No, why it should get lost?
The process i did was:
1) Boot at bootloader ([POWER]+[VOL-])
2) fastboot flash bootloader <bootloader.img>
3) fastboot flash radio <radio.img>
4) Start recovery (TWRP)
5) Flash stock-4.3 zip
6) Flash SuperSU zip
That's all. Neither recovery, nor userdata were touched through this process. The only affected partitions are bootloader, radio, system, boot and data.
Click to expand...
Click to collapse
i just full wipe my tilapia.. lolx.. anyway, i have backup all of my apps in zip file.. hahaha
one thing can confirm is no need flash bootloader.. i didnt flash it still ok.. but radio i not sure yet..because dont have simcard right now..lolx
Gabrieltan said:
i just full wipe my tilapia.. lolx.. anyway, i have backup all of my apps in zip file.. hahaha
one thing can confirm is no need flash bootloader.. i didnt flash it still ok.. but radio i not sure yet..because dont have simcard right now..lolx
Click to expand...
Click to collapse
You mean you download zip file from OP, then flash it in TWRP?
Sent from my GT-N7105 using Tapatalk 4 Beta
zard said:
You mean you download zip file from OP, then flash it in TWRP?
Sent from my GT-N7105 using Tapatalk 4 Beta
Click to expand...
Click to collapse
yup.. without flash bootloader.. now trying for titanium.. where can change the storage thing?
Gabrieltan said:
yup.. without flash bootloader.. now trying for titanium.. where can change the storage thing?
Click to expand...
Click to collapse
This is Chainfire's information: You can fix this by going into preferences and selecting a folder under /storage/emulated/legacy as backup/restore path, not under /storage/emulated/0
I think it means that you copy your files from /storage/emulated/0 to /storage/emulated/legacy, then rescan backup directory and set to /storage/emulated/legacy.
Sent from my GT-N7105 using Tapatalk 4 Beta
zard said:
This is Chainfire's information: You can fix this by going into preferences and selecting a folder under /storage/emulated/legacy as backup/restore path, not under /storage/emulated/0
I think it means that you copy your files from /storage/emulated/0 to /storage/emulated/legacy, then rescan backup directory and set to /storage/emulated/legacy.
Sent from my GT-N7105 using Tapatalk 4 Beta
Click to expand...
Click to collapse
that is what i did just now... and it cause i lost my root for tb.. now trying clear data, forget root and rerun the application
Gabrieltan said:
i just full wipe my tilapia.. lolx.. anyway, i have backup all of my apps in zip file.. hahaha
one thing can confirm is no need flash bootloader.. i didnt flash it still ok.. but radio i not sure yet..because dont have simcard right now..lolx
Click to expand...
Click to collapse
Yeah, i forgot to say that i full wiped first, of course (not sure if it's mandatory, though). Bootloader and radio may not be so important, as after i flashed them 4.2.2 booted successfully (before installing 4.3) which might be a sign that not much of a difference was made.
Gabrieltan said:
yup.. without flash bootloader.. now trying for titanium.. where can change the storage thing?
Click to expand...
Click to collapse
Just go on to Menu->Preferences... . There is an option about the location of the backups (the first option under Backup Settings). If you press on it you get on /storage/emulated/0/TitaniumBackup but you change that to /storage/emulated/legacy/TitaniumBackup. Practically, it's the same folder (nothing needs to be copied or anything) but it's just on a different mount point and for some reason (i am guessing permissions) it does work. If it asks you to copy any other backups just don't do it, everything is already there.
stadicon said:
Just go on to Menu->Preferences... . There is an option about the location of the backups (the first option under Backup Settings). If you press on it you get on /storage/emulated/0/TitaniumBackup but you change that to /storage/emulated/legacy/TitaniumBackup. Practically, it's the same folder (nothing needs to be copied or anything) but it's just on a different mount point and for some reason (i am guessing permissions) it does work. If it asks you to copy any other backups just don't do it, everything is already there.
Click to expand...
Click to collapse
LOLx... i did that and now my backup all lose.. urs still at there?? one more thing, you able use tb to delete apps??
There should be no way to lose your backups unless you have chosen purposely to do so. Check that your Titanium Backups folder is still there in SDCARD.
If I weren't on vacation using only Chromebook I'd have upped this this morning with root; I managed via ARM Chromebook dev mode with adb and fastboot to backup data from my N4 and N7 3G and then install stock, flash recovery and make root, followed by restoring my titanium data. Both devices were as they were in 4.2.2 but in 4.3 within the hour.
Furthermore I had the ability to flash Franco r170 on the N4
Gabrieltan said:
LOLx... i did that and now my backup all lose.. urs still at there?? one more thing, you able use tb to delete apps??
Click to expand...
Click to collapse
Just use a file manager to make sure everything is fine. Technically, /storage/emulated/0/TitaniumBackup and /storage/emulated/legacy/TitaniumBackup is the same folder, i don't know why TB does't list your backups.
BTW, i think the battery drain issue is now fixed.
stadicon said:
Just use a file manager to make sure everything is fine. Technically, /storage/emulated/0/TitaniumBackup and /storage/emulated/legacy/TitaniumBackup is the same folder, i don't know why TB does't list your backups.
Click to expand...
Click to collapse
i also dont know why.. but i can backup... ya, only can use root explorer to delete, i tried few apps, all cant delete..
gapps hosted here works: http://forum.xda-developers.com/showthread.php?t=2248654
I got the notification to install and I tried. Shield restarted and the little green android guy showed up and it started installing the update. Half way through it showed a red explanation mark with the words "error". I had to hold down the shield+home keys to restart. The shield restarted just fine. I deleted the data in google frameworks (read to do that here) and tried the update again, same outcome.
I'm new to android (came from iphone) and now have a galaxy S4. So I apologize about the noobiness.
My shield is rooted and bootloader unlocked. As far as I know I did not install any custom recovery. I thought that users should be able to install OTA if they are running the stock OS and no custom recoveries. Am I wrong about that? Anyways, I have SuperSU installed along with a few rooted apps. My guess is that I will need to install a custom recovery so I can flash this update, is this correct? I would be very grateful if someone would explain whats going on here =P
You should not need a custom recovery for this.
Due to the download size of this update it appears to be an incremental update.
the download size i see is 22.3 MB
You would need to see the exact error to try an figure out more.
UPDATE
Installed fine for me
Custom recovery is definitely not needed. Root by itself also does not interfere. I updated without trouble.
Maybe try reflashing the boot and system partitions to stock and try the update again?
Gnurou said:
Custom recovery is definitely not needed. Root by itself also does not interfere. I updated without trouble.
Maybe try reflashing the boot and system partitions to stock and try the update again?
Click to expand...
Click to collapse
a quick how to on reflashing the boot and system would be awesome!!
--edit:nevermind... im trying out Kwonggers program--
ok somehow i softbricked my shield. I've tried Kwonggers program and I've manually flashed recovery,boot, and system and afterwards all I get is the flashing green controller during boot. I know I did it right because all messages were positive.
I also downloaded the most up to date shield files from nvidia (update64) which is extract-nv-recovery-image-shield-01.00.13216_261.5912.sh however I dont know how to use a *sh file.
Rhokk said:
a quick how to on reflashing the boot and system would be awesome!!
--edit:nevermind... im trying out Kwonggers program--
ok somehow i softbricked my shield. I've tried Kwonggers program and I've manually flashed recovery,boot, and system and afterwards all I get is the flashing green controller during boot. I know I did it right because all messages were positive.
I also downloaded the most up to date shield files from nvidia (update64) which is extract-nv-recovery-image-shield-01.00.13216_261.5912.sh however I dont know how to use a *sh file.
Click to expand...
Click to collapse
it needs a factory rest.
my suggestion is to re-flash system (again) using the command fastboot -w flash system system.img
the .sh file is for use on Linux, cygwin can probably do that if you have the correct things installed with it.
chevyowner said:
it needs a factory rest.
my suggestion is to re-flash system (again) using the command fastboot -w flash system system.img
the .sh file is for use on Linux, cygwin can probably do that if you have the correct things installed with it.
Click to expand...
Click to collapse
Chevyowner you are the best! After reading your suggestion, I tried just the system.img this time and presto! This time it took. Not sure why it didn't take the 2 times I tried it last night.
Thanks for helping newer guys like me. Really appreciate it!
Rhokk said:
Chevyowner you are the best! After reading your suggestion, I tried just the system.img this time and presto! This time it took. Not sure why it didn't take the 2 times I tried it last night.
Thanks for helping newer guys like me. Really appreciate it!
Click to expand...
Click to collapse
glad you got it working
chevyowner said:
glad you got it working
Click to expand...
Click to collapse
hi.
i am a new guy from far far away China, language is the biggist problem.
the same issue, i can't fix it, error in updating ota 65.
re-flash system (again) using the command fastboot -w flash system system.img
Click to expand...
Click to collapse
how to do? where i can get /system.img/? and how to push the img to my Shield?
except a PC and a cable, i don't have any tools, no software. and i can't get that what you guys talking about. but the same issue.
if you guys can help, i will be very appreciated
if u do know Chinese.....=P
Hi, I have the same issue, OTA 64 installed with bootloader unlocked and rooted. Will my data be preserved if I flash only the system image?
Nikojiro said:
Hi, I have the same issue, OTA 64 installed with bootloader unlocked and rooted. Will my data be preserved if I flash only the system image?
Click to expand...
Click to collapse
how can you get the /system image/? thanks
starfriend.y said:
how can you get the /system image/? thanks
Click to expand...
Click to collapse
Here's how I fixed my system:
Downloaded OTA 65 image from https://developer.nvidia.com/develop4shield
As per instructions (see https://developer.nvidia.com/sites/default/files/akamai/mobile/shield/HowTo-Flash-Recovery-Image_1.txt), flashed only boot, recovery and system images (so it wouldn't wipe your user partition, e.g. apps and data)
Rebooted the unit, waited for the upgrade to complete. Root will be lost if you had it.
Rerooted the unit (see https://github.com/linux-shield/shield-root)
It works perfectly now.
Nikojiro said:
Here's how I fixed my system:
Downloaded OTA 65 image from https://developer.nvidia.com/develop4shield
As per instructions (see https://developer.nvidia.com/sites/default/files/akamai/mobile/shield/HowTo-Flash-Recovery-Image_1.txt), flashed only boot, recovery and system images (so it wouldn't wipe your user partition, e.g. apps and data)
Rebooted the unit, waited for the upgrade to complete. Root will be lost if you had it.
Rerooted the unit (see https://github.com/linux-shield/shield-root)
It works perfectly now.
Click to expand...
Click to collapse
thanks for your help.
is that /ota 65 image/ a 1.0GB .sh file? i can't unzip it.
i think that i have to unzip the .sh file with a linux pc.
starfriend.y said:
thanks for your help.
is that /ota 65 image/ a 1.0GB .sh file? i can't unzip it.
i think that i have to unzip the .sh file with a linux pc.
Click to expand...
Click to collapse
Yes the .sh file is a linux shell script. I can repack it in a standard zip and upload it later today on a share if you want.
Sent from my GT-I9100 using Tapatalk
Ok I uploaded a repacked zip of the OTA 65 images for linux-less people
https://mega.co.nz/#!ccRCQTAS!FylQx29ZE7RUvi-kzbwb53woZGRZUu9_RAQNk9_FkMI
Please note that you'll need to have the Android SDK installed, as well as the proper USB driver.
Nikojiro said:
Ok I uploaded a repacked zip of the OTA 65 images for linux-less people
https://mega.co.nz/#!ccRCQTAS!FylQx29ZE7RUvi-kzbwb53woZGRZUu9_RAQNk9_FkMI
Please note that you'll need to have the Android SDK installed, as well as the proper USB driver.
Click to expand...
Click to collapse
thanks a lot! you are so kind!
Nikojiro said:
Ok I uploaded a repacked zip of the OTA 65 images for linux-less people
https://mega.co.nz/#!ccRCQTAS!FylQx29ZE7RUvi-kzbwb53woZGRZUu9_RAQNk9_FkMI
Please note that you'll need to have the Android SDK installed, as well as the proper USB driver.
Click to expand...
Click to collapse
here i come again...
as your guide, i've flash my Shield /recovery.img/ and /boot.img/, they all done. but failed when i flash /system.img/, "FAILED (remote: insufficient memory)"
why?
starfriend.y said:
here i come again...
as your guide, i've flash my Shield /recovery.img/ and /boot.img/, they all done. but failed when i flash /system.img/, "FAILED (remote: insufficient memory)"
why?
Click to expand...
Click to collapse
Hi, sorry with so little background information I'm afraid I can't help. I'd recommend a full reflash of your unit.
Sent from my GT-I9100 using Tapatalk
Nikojiro said:
Hi, sorry with so little background information I'm afraid I can't help. I'd recommend a full reflash of your unit.
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
thank you first.
I do as you said, download the file, unzip it, and i got /system.img/, /boot.img/ and /recovery.img/.
i opened cmd and type /fastboot flash system system.img/ and i got failed information: /FAILED (remote: insufficient memory)/
im sure i wipe my shield first, and i flash recovery, boot very well.
can't update
hello,
I would very much appreciate some real help.
I want to be able to update to 65 WITHOUT loosing my userdata. I very much care for all my settings, software and setup.
I am bootloader unlocked from the very beginning and rooted. I was able to update OTA just fine until this update, and the root back very easily each time afterwards.
I knew that this ($#@@ing) delta update will give me trouble so I made some research first. With no use... I still couldn't update..
What I did:
-> downloaded custom CMW for shield and booted. made a nandroid (again: I very much care for my data and I won't update until and can do it without wiping) - all fine
-> downloaded the extracted image of OTA 65 from this thread, booted into boot loader and did:
fastboot flash recovery recovery.img
- OK
fastboot flash boot boot.img
- OK
fastboot flash system system.img
- insufficient memory crap.. (hoped I won't get it but... (( )
-> booted back into JB.. booted fine but my SD card storage partition wasn't where file managers read it anymore (it was mounted and OK on /system/storage but just lost some symlink of some sort... no big deal.. I guess it was the new bootloader at fault but since the 65 system image wasn't flashed I guessed it will work again afterwards..)
-> opened supersu, full unrooted, took a leap of fate and tried the delta update OTA... gave me the killed andoid at about 50% (
-> tried fastboot flash system system.img on another computer.. insufficient memory crap again....
-> so I booted again into CMW and restored my nandroid. Luckily everything worked fine...
So if someone knows how can I go 65 without userdata wipe, please help me!
thank you very much
Same problem here
Surprise, surprise! .... =(
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
//cc @Nikojiro
this Recovery is now depreciated go https://forum.xda-developers.com/showthread.php?p=71244945 instead
What's new
MTP auto mount on boot fixed!
Data unmount after few seconds fixed.
Bugs
Battery Info doesn't work (due to M based sources)
Data decryption
Mount Loop devices (Kernel issue) can't be fixed atm
Credits: TWRP (Team win Recovery Project)
Huawei
@BadWolfYe for giving info on how he got MTP working.
Me
Current status: Stable
Created: 2016-11-20
Removed
LastStandingDroid said:
This was shared here for reasons that some P9 users came to our H8 thread so i decided to post it here as well.
Click to expand...
Click to collapse
Thank you so much for your hard work. When you say data works but requires reflash could you explain which part requires reflash?
Regards
Lee
Just to clarify, does this allow mounting and editting of /system partition, manually via TWRP terminal?
Atarii said:
Just to clarify, does this allow mounting and editting of /system partition, manually via TWRP terminal?
Click to expand...
Click to collapse
Yes you can mount cust, data, system, product, vendor
thel2dab said:
Thank you so much for your hard work. When you say data works but requires reflash could you explain which part requires reflash?
Regards
Lee
Click to expand...
Click to collapse
The properdata fix will flash a empty image to the phone which you'll have to resize after flash or I'll get 2.Gb of internal storage only.you might need repair data first or reboot recovery for it to be repairable.
Sent from my FRD-L09 using Tapatalk
U are best.
Does flashing ROM's work?
I whant to flash newest N emui 5.0 wihout roolback
I don't know why but my phone fails to boot after flashing the properdatafix.zip and resizing.
It resizes correctly but after it won't boot. I have to flash old firmware and upgrade to to 7.0 again.
Any help would be great.
Regards
Lee
richish said:
U are best.
Does flashing ROM's work?
I whant to flash newest N emui 5.0 wihout roolback
Click to expand...
Click to collapse
It flashes firmwares yes I've reflashed N and the hw_EU full package
thel2dab said:
I don't know why but my phone fails to boot after flashing the properdatafix.zip and resizing.
It resizes correctly but after it won't boot. I have to flash old firmware and upgrade to to 7.0 again.
Any help would be great.
Regards
Lee
Click to expand...
Click to collapse
Exactly what did you flash? AFAIK if it is a zip that mounts a image it will either bill the flash process with a reboot or make your device stuck on splash screen. What zip did u use?
If.u flashed N pack from M twrp u can install it again with this twrp. If it doesn't boot then it's probably due to a Img (ext4) that is being mounted and that's most likely is due to modified boot.img which will kill the boot procedure supersu package can make a modified boot but it won't boot due to su.img being mounted so it'll reboot to recovery
Sent from my FRD-L09 using Tapatalk
LastStandingDroid said:
Exactly what did you flash? AFAIK if it is a zip that mounts a image it will either bill the flash process with a reboot or make your device stuck on splash screen. What zip did u use?
Click to expand...
Click to collapse
I flashed the properdatafix.zip from the 1st post. Then rebooted in to twrp went to wipe - advanced wipe - data - resize partion - reboot - stuck on black screen.
fastboot flash, recovery, boot, system, from stock to get device booting again.
I must be doing something wrong. I know this is really cheeky to ask but could you make a video or something of the correct flashing procedure? The way I have tried is like this:
1 Fastboot flash your recovery.img
2. Boot into TWRP recovery.
3. Install properdatafix.zip
4. Reboot recovery.
5. Resize data partition.
6. Reboot and phone wont boot anymore.
Regards
Lee
thel2dab said:
I flashed the properdatafix.zip from the 1st post. Then rebooted in to twrp went to wipe - advanced wipe - data - resize partion - reboot - stuck on black screen.
fastboot flash, recovery, boot, system, from stock to get device booting again.
I must be doing something wrong. I know this is really cheeky to ask but could you make a video or something of the correct flashing procedure? The way I have tried is like this:
1 Fastboot flash your recovery.img
2. Boot into TWRP recovery.
3. Install properdatafix.zip
4. Reboot recovery.
5. Resize data partition.
6. Reboot and phone wont boot anymore.
Regards
Lee
Click to expand...
Click to collapse
You can install the firmware again after you resized the data partition if something goes wrong and report back if it helps. Maybe it is a block issue in fstab but it shouldn't be
Sent from my FRD-L09 using Tapatalk
@LastStandingDroid
I also will not boot in the system...
What file system (data) should be displayed in TWRP, ext4?
LastStandingDroid said:
You can install the firmware again after you resized the data partition if something goes wrong and report back if it helps. Maybe it is a block issue in fstab but it shouldn't be
Sent from my FRD-L09 using Tapatalk
Click to expand...
Click to collapse
How should I install the firmware again? Through flashable zip or through dload folder and hold vol up and down when restarting phone? Thank you for your patience, I know I am taking a lot of your time with this.
Regards
Lee
kep2008 said:
@LastStandingDroid
I also will not boot in the system...
What file system (data) should be displayed in TWRP, ext4?
Click to expand...
Click to collapse
The data should be ext4 format. Could u mount system and check if there's any file in system folder also u might need to resize system as well since u only have 19mb as well.
thel2dab said:
How should I install the firmware again? Through flashable zip or through dload folder and hold vol up and down when restarting phone? Thank you for your patience, I know I am taking a lot of your time with this.
Regards
Lee
Click to expand...
Click to collapse
Sent from my FRD-L09 using Tapatalk
thel2dab said:
How should I install the firmware again? Through flashable zip or through dload folder and hold vol up and down when restarting phone? Thank you for your patience, I know I am taking a lot of your time with this.
Regards
Lee
Click to expand...
Click to collapse
I'd use twrp to flash it.since u won't have to roll back again
Sent from my FRD-L09 using Tapatalk
LastStandingDroid said:
I'd use twrp to flash it.since u won't have to roll back again
Sent from my FRD-L09 using Tapatalk
Click to expand...
Click to collapse
Thanks. It seems to reflash ok in TWRP but after the flash completes. I need to factory reset but I am back to to stock recovery. It seems that flashing the update.zip overwrites the recovery. (I assume this is expected?)
Thanks again for your help. Is there is anything else I can try to get this to work?
Regards
laststandingdroid said:
the data should be ext4 format. Could u mount system and check if there's any file in system folder also u might need to resize system as well since u only have 19mb as well.
Sent from my frd-l09 using tapatalk
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Again install update.zip 7.0, but the system will not boot...
thel2dab said:
Thanks. It seems to reflash ok in TWRP but after the flash completes. I need to factory reset but I am back to to stock recovery. It seems that flashing the update.zip overwrites the recovery. (I assume this is expected?)
Thanks again for your help. Is there is anything else I can try to get this to work?
Regards
Click to expand...
Click to collapse
Yes the recovery is replaced after flash back stock. Did it boot after reflashed?
Strange are you having Vendor And product option available in Mount restore and backup? To see if they are properly flashed?
kep2008 said:
View attachment 3948500View attachment 3948501
Again install update.zip 7.0, but the system will not boot...
Click to expand...
Click to collapse
Did you get the data to work in TWRP? I think the boot.img is the issue here tbh. Since I neither can't boot unless I use a supersu fixed image.
Sent from my FRD-L09 using Tapatalk
Ok w8 I'll fix a twrp that will make the installation of su system less mode possible but u will be forced to remove su.img from /data/ else it won't boot
fastboot flash this: http://www21.zippyshare.com/v/7YNPp3AI/file.html
Before You Flash SuperSU-Systemmode you need to mount system & /vendor first since the Sepolicy is located in the "Vendor" Partition for reasons i won't bother to explain.
Once Flashed Mount Data again (if it gets unmounted, mount system) and navigate to /data and remove su.img
This will make N booting
Sent from my FRD-L09 using Tapatalk
LastStandingDroid said:
Yes the recovery is replaced after flash back stock. Did it boot after reflashed?
Strange are you having Vendor And product option available in Mount restore and backup? To see if they are properly flashed?
Did you get the data to work in TWRP? I think the boot.img is the issue here tbh. Since I neither can't boot unless I use a supersu fixed image.
Sent from my FRD-L09 using Tapatalk
Click to expand...
Click to collapse
/data is mounted only with /system, but the installation files still contain errors /data/media
mount -o bind /data/media /sdcard process ended with ERROR 255
kep2008 said:
/data is mounted only with /system, but the installation files still contain errors /data/media
mount -o bind /data/media /sdcard process ended with ERROR 255
Click to expand...
Click to collapse
Did u use the new recovery? If so that is for now common since it uses a different mount file rather than busbox version) that's why this message comes
In fact I copied over the "original" mount file from stock recovery but it isn't copying the compete file as it's only 6b so it'll stay until I try fix it.
Sent from my FRD-L09 using Tapatalk