Related
Hi guys, I hope you can help me.
I have just rooted + flashed my motorola defy plus for the first time (on any device for that matter)
I installed 2nd init, version 0.6.... or something.
Put a rom, kernel and google apps on my sd-card
Then I turned usb-debugging off and rebooted my phone.
Now I can get into bootmenu, and this is what I do:
1) go to recovery
2) select custom recovery
3) then it says: Clockworkmod Recovery v2.5.1.8
E: Can't open /tmp/recovery.log
4) I then select wipe data/factory reset
5) then it says this: Formatting DATA
Formatting CACHE
FORMATTING SDEXT
No app2sd partition found. Skipping format of /sd-ext
Formatting SDCARD:/.android_secure
Data wipe complete
E: Can't open /tmp/recovery.log
6) After that i select install zip from sdcard
7) then I select choose zip from sdcard
8) then I select the zip file containing the rom
9) And it says: Finding update package
Opening update package
Installing update
E: Can't make /tmp/update_binary
Installation aborted
Now I can't go any further and can't use my phone at all
I hope u guys can help me, and that I haven't F*ed up my phone
I have a quite similar problem.
On a defy+,rooted 2ndinit installed, backup-ed first, download the new quarx05/03 ICS, put the zip on sd, wipe data, reboot and start to install ics, but the message was
''Finding update package
Installing update
E: Can't make /tmp/update_binary
Installation aborted"
Thanks to the previously backup I can use may phone as usual.
What I have done wrong with de ICS installation?
Thanks
PS. Sorry for probable a dummie question:What we have to do with md5 zip near the CM9 Jordan.zip?
A little help please about the subject?
Thank you
ics
The entire process
ClockworkMode v2.5.1.8
Wipping data...
Formatting DATA...
Formatting CACHE...
Formatting SDEXT..
No app2sd partition found.Skipping format of /sd-ext.
Formatting SDCARD: /.android_secure...
Data wipe complete
E: Can't open /tmp/recovery.log...
Installing: SDCard:download/CM9-ICS-MR1-120305-jordan.zip
Finding update package
Opening update package
Installing update
E: Can't make /tmp/update_binary
Installation aborted
if try Wipe Dalvik Cache:
E: Can't mount /dev/block/mmcblk0p2
(No such file or directory)
I guess that this is a simple and many times occured error, since nobody has any answer....
Does you disabled the usb debugging before flashing?
Yes I do, but nothing change,
Thanks
if I'm not mistaken the last release of 2nd init is not compatible with defy. Try to check this on the development forum. I hope I have been of help.
I'd tried with both 1.0.7 latest and 0.6.1.
With latest, the phone is blocked.
Thanks
I had used this. Try with it
P.S. sorry for my bad english.
Tried, the same errors,
Thanks
I don't know. Sorry. By the time i had used that.
I think you need to go to stable recovery after you wipe your data from custom recovery
Sent from my MB525 using xda premium
I think you need to go to stable recovery after you wipe your data from custom recovery
What do you mean by "stable recovery"? You talk about version 0.6. of 2nd init or something else?
Can you show a step-by step procedure?
Thank you in advance.
However, which is the procedure to un-root a defy+ and to have it with the original, fresh system?
I had flash a new SBF, root with Unlockroot v2.3, anything else doesn't work, 2ndinit v2.0 stable, wipe data/cache/dalvik (same errors), try to install cm9-ics, the same error "Can't make /tmp/update_binary"
What the f.....?
cretu22 said:
I had flash a new SBF, root with Unlockroot v2.3, anything else doesn't work, 2ndinit v2.0 stable, wipe data/cache/dalvik (same errors), try to install cm9-ics, the same error "Can't make /tmp/update_binary"
What the f.....?
Click to expand...
Click to collapse
Hi, I have exactly the same problem.. Trying to find a solution but is quite difficult. First I thought it has something to do with the partitioning, as stated in THIS topic. But, in THIS topic, people say that partitioning the SD card is not necessary at all..
@Cretu22: Yes stable recovery is CWM 0.6
Don't install stable recovery! I too faced this issue when I flashed using stable recovery. In snd init install Latest recovery and then try flashing your ROM. That should work..
I did choose the stable version indeed 0.6.7.
Now i did uninstall it and installed the latest 1.0.7, but when I reboot my phone it won't get into the boot menu but just boots into android. Tried it several times, but only with 0.6.7 I seem to be able to get in the menu
fokkeh said:
I did choose the stable version indeed 0.6.7.
Now i did uninstall it and installed the latest 1.0.7, but when I reboot my phone it won't get into the boot menu but just boots into android. Tried it several times, but only with 0.6.7 I seem to be able to get in the menu
Click to expand...
Click to collapse
Okay!! I hope you were pressing the volume down button when the blue LED came?? Try doing this again all over.. I mean reinstall 2nd init and then latest recovery.. I remember doing this once(instal latest recovery after I installed stable recovery)..
pranks1989 said:
Okay!! I hope you were pressing the volume down button when the blue LED came?? Try doing this again all over.. I mean reinstall 2nd init and then latest recovery.. I remember doing this once(instal latest recovery after I installed stable recovery)..
Click to expand...
Click to collapse
Yes, its working Pressing the volume down button was not necessary with 0.6.7, that was what went wrong. Now the zips installed like a charm
i know the answer and is very simple
the problem is that you cannot create that specific folder.... because it already exist, cmp (connected music player) creates it, just delete it from SD and done!
Hi guys!
I did a backup of stock rom using cwm. then restored a backup of cm7. on restoring, it gave me this error:
ERROR MOUNTING /SYSTEM!
RESTORE FAILED.
so i rebooted my phone. now it get soft bricked. i can open recovery. in stock recovery, i can see all the recovery options but at the bottom its written
APPLING MUTI-CSC
RFS- FAILED TO MOUNT /SYSTEM (INVALID ARGUMENT)
yes.. spellings are written wrong on recovery.
if i goto cwm and restore nandroid backup of stock recovery, its giving error that
ERROR MOUNTING /SYSTEM
RESTORE FAILED
i tried formatting system via cwm, but it gave me error that
ERROR MOUNTING /SYSTEM
SKIPPING FORMAT..
DONE.
i tried flashing other kernels via cwm but it didnt help. also i cannot use odin (it takes upto 1-2 hrs trying for odin to detect my phone)
i am going to flash cm7.. i dont know if it will help or not..
pleaseeeeeeeeeeee help..
UPDATE: I think dat it will help if anyone could give a backup of /system dir in form of flashable zip (with commands like mkdir etc to remake system dir),, then it would be gr8..
If you a restoring a nandriod backup of cm7 you need to flash percys kernel first (I presume you were using that kernel when you were using cm7 as that is required) then reboot to recovery wipe system data cache then you can restore your nandriod backup
Change kernel to stock using hell fusion and format system and mount
Gửi từ Galaxy Y bằng cách sử dụng tia X truyền từ mặt trời!
If you have a nandroid backup of percy's cm7 then try flash stock rom via odin. Then go to stock recovery and flash percy's CyanogenMod7#2 kernel. Reboot phone and go to recovery again... You will must see CWM recovery and then try restore your nandroid backup.
Sorry for bad English
1. Flash percy's kernel.
2. then reboot recovery
3. format system. format data. format cache. mount all of them (system may not mount)
4. flash cm7 rom
5. reboot system.. (still bricked)
6. take out battery and re insert
boot into cwm, u will see many errors
7. flash cm rom again (3 times) (see steps3&4 for info)
8. reboot (still bricked)
9. boot into cwm. now all errors gone. format all and mount all of them (system will mount)
9. flash hyperion rom
10. fix permissions
11. reboot system now
12. fixed!
techmentry said:
1. Flash percy's kernel.
2. then reboot recovery
3. format system. format data. format cache. mount all of them (system may not mount)
4. flash cm7 rom
5. reboot system.. (still bricked)
6. take out battery and re insert
boot into cwm, u will see many errors
7. flash cm rom again (3 times) (see steps3&4 for info)
8. reboot (still bricked)
9. boot into cwm. now all errors gone. format all and mount all of them (system will mount)
9. flash hyperion rom
10. fix permissions
11. reboot system now
12. fixed!
Click to expand...
Click to collapse
thanks!!!!! that worked
Say, i come from another ROM.
I was using resurrection remix kitkat the final version and i actually used the CM theme chooser to change some styles and boot animations.
I am aware it can cause system crashes but the last time it crashed, it gave me the exact same errors with a frozen s III logo. Refused to boot, soft brick with access to both odin mode and cwm recovery of resurrection, unable to mount /sdcard (E
Will this procedure work on my device GTi9300 or should i keep looking for more?
I tried flashing
1) stock rom but connection hangs
2) Stock recovery NANDWRITE fails
3) PIT file but gets stuck on Get pit mapping thingy
4) and occasionally it just freezes at establishing connection
I tried pushing the file through abd but it doesn't detect once it reboots to bootloader on fastboot.
MavPinch said:
Say, i come from another ROM.
I was using resurrection remix kitkat the final version and i actually used the CM theme chooser to change some styles and boot animations.
I am aware it can cause system crashes but the last time it crashed, it gave me the exact same errors with a frozen s III logo. Refused to boot, soft brick with access to both odin mode and cwm recovery of resurrection, unable to mount /sdcard (E
Will this procedure work on my device GTi9300 or should i keep looking for more?
I tried flashing
1) stock rom but connection hangs
2) Stock recovery NANDWRITE fails
3) PIT file but gets stuck on Get pit mapping thingy
4) and occasionally it just freezes at establishing connection
I tried pushing the file through abd but it doesn't detect once it reboots to bootloader on fastboot.
Click to expand...
Click to collapse
Please check where you are posting before you post - this forum is for the galaxy y 5360
As a general rule when restoring backups
1- restore the backup using the same kernel to which the backup was made
2- restore the backup using the same recovery version to which the recovery was made
When flashing stock rom via odin make sure you have the Samsung USB driver installed
Never flash bootloader or pit unless you know what you are doing - they are not needed for typical stock rom flashing
Goto your own phone forum for support on flashing stock rom for your device
marcussmith2626 said:
Please check where you are posting before you post - this forum is for the galaxy y 5360
As a general rule when restoring backups
1- restore the backup using the same kernel to which the backup was made
2- restore the backup using the same recovery version to which the recovery was made
When flashing stock rom via odin make sure you have the Samsung USB driver installed
Never flash bootloader or pit unless you know what you are doing - they are not needed for typical stock rom flashing
Goto your own phone forum for support on flashing stock rom for your device
Click to expand...
Click to collapse
Gotcha. Just poking around here and there because i haven't been able to work it.
techmentry said:
1. Flash percy's kernel.
2. then reboot recovery
3. format system. format data. format cache. mount all of them (system may not mount)
4. flash cm7 rom
5. reboot system.. (still bricked)
6. take out battery and re insert
boot into cwm, u will see many errors
7. flash cm rom again (3 times) (see steps3&4 for info)
8. reboot (still bricked)
9. boot into cwm. now all errors gone. format all and mount all of them (system will mount)
9. flash hyperion rom
10. fix permissions
11. reboot system now
12. fixed!
Click to expand...
Click to collapse
Now nothing formats or mounts, any ideas why?
Hi, I am in the process of preparing for upgrading from 7.0 to 7.1.1
I know I need to replace the Custom Kernel with the Stock Kernel. And I have to replace TWRP with Stock Recovery.
Can anybody tell me, which file inside the FTF is the stock recovery? I already found the kernel. Need help to find the stock recovery, thank you!
tempurastyle said:
Need help to find the stock recovery, thank you!
Click to expand...
Click to collapse
We don't have one which is why we have to use TWRP.
So my only way is to flash via Flashtool without wipe?
tempurastyle said:
So my only way is to flash via Flashtool without wipe?
Click to expand...
Click to collapse
Do that then mod your own kernel. [How To] make your own XPERIA DRM-fix kernel.
And flash a TWRP.img to the recovery partition.
fotakernel.sin reside's where we flash twrp on stock. you do not need to flash it to upgrade, contrary you can exclude it in flashtool and keep twrp between updates.
realtuxen said:
fotakernel.sin reside's where we flash twrp on stock. you do not need to flash it to upgrade, contrary you can exclude it in flashtool and keep twrp between updates.
Click to expand...
Click to collapse
this is real knowledge, thanks! so just to be sure, this is what i will do in flashtool:
1) wipe: nothing selected
2) exclude: fotakernel.sin selected
can anybody confirm this is correct?
then after this, i will flash a custom kernel via fastboot and magisk via twrp.
one question regarding magisk: will it be deleted during the flashtool update?
So I ran into a problem...
The Upgrade to 7.1.1 via flashtool was smooth. Then, i flashed twrp via fastboot as usual. When I tried to enter twrp, i get a password prompt to decrypt the phone. So i don't know which password i need to type in. I tried the unlock PIN, doesnt work. Any suggestions?
tempurastyle said:
Any suggestions?
Click to expand...
Click to collapse
To get round that you need to run the following commands...
Code:
fastboot format userdata
fastboot format cache
...so you'll need to backup all your data first.
XperienceD said:
To get round that you need to run the following commands...
Code:
fastboot format userdata
fastboot format cache
...so you'll need to backup all your data first.
Click to expand...
Click to collapse
Ok, so I decided to keep my data and don't install twrp. Now I got another issue, is it possible to install Magisk without TWRP? I already got my kernel using my ta backup according to the instructions a few posts above, which really works great.
tempurastyle said:
Ok, so I decided to keep my data and don't install twrp. Now I got another issue, is it possible to install Magisk without TWRP? I already got my kernel using my ta backup according to the instructions a few posts above, which really works great.
Click to expand...
Click to collapse
I thought you excluded fotakernel so you did not have to flash twrp again. Oh well anyway you can use twrp to flash zips just fine although /data is encrypted, most flash zips do not write to /data anyway some like supersu use /cache (which is not encrypted contrary to the info above) to get around encryption at next boot. And like magisk also patch the boot.img live on your phone, some write to /system which is not encrypted either, I never seen a flash zip that did write to /data. Only backup/browsing/etc on /data is affected.
So when presented with the password screen in twrp just press cancel and make sure the zip you want to flash is located on the external sd card (do not encrypt this in phone settings, your card will be unreadable from pcs to) then choose flash zip and choose the external sdcard to pick the zip from and flash magisk or whatever. You need to run your kernel through ta poc or rootkernel first and disable dm verity and sony ric. (you write you did this so just install twrp and flash away) Do not wipe cache before rebooting just in case magisk uses this in a similar way to supersu (I have no idea)
Also if you do the above fastboot format commands suggested in post#8 without disabling 'forceencrypt' for /data (fstab in the kernel image or with a tool) the phone will encrypt itself again as soon as you turn it on.
If forceencrypt is disabled the same can be achieved (clearing encryption) with a factory reset btw.
So if you did not bump into the password in twrp before you likely did a factory reset with a kernel with encryption disabled. Then, maybe after updating you rebooted stock and the phone encrypted itself again, then now you can not access /data in twrp. Thats also because we have no version of it that supports encryption on the X-compact though. Again do not worry, I have not meet a zip I could not flash, supersu, magisk, etc because they do not access /data anyway.
realtuxen said:
I thought you excluded fotakernel so you did not have to flash twrp again. Oh well anyway you can use twrp to flash zips just fine although /data is encrypted, most flash zips do not write to /data anyway some like supersu use /cache (which is not encrypted contrary to the info above) to get around encryption at next boot. And like magisk also patch the boot.img live on your phone, some write to /system which is not encrypted either, I never seen a flash zip that did write to /data. Only backup/browsing/etc on /data is affected.
So when presented with the password screen in twrp just press cancel and make sure the zip you want to flash is located on the external sd card (do not encrypt this in phone settings, your card will be unreadable from pcs to) then choose flash zip and choose the external sdcard to pick the zip from and flash magisk or whatever. You need to run your kernel through ta poc or rootkernel first and disable dm verity and sony ric. (you write you did this so just install twrp and flash away) Do not wipe cache before rebooting just in case magisk uses this in a similar way to supersu (I have no idea)
Click to expand...
Click to collapse
Yes, after the first upgrade attempt, i let twrp untouched. then when entering twrp, i didnt have a password, so i skipped it. i couldn't find the sd card in the file browser, and after i hit reboot in twrp the phone restarted and got stuck in boot.
So I flashed again, this time deleting twrp. the initial boot up went fine. Then i flashed twrp again and once again, without having a password, i just skipped the password prompt. still couldnt find the sd card, and i rebooted out of twrp. and the phone got stuck again.
after 2-3 trials, i figured out that everytime i rebooted out of twrp, the phone gets stuck during boot. even after turning it off and on, so a reflash was needed.
now i have given up using twrp, so i have an unrooted phone with an unlocked bootloader. which does not allow me to use android pay. i think to solve my problem is:
1) i need to know which twrp version really works, i have tried
this version
and this version
both cause a boot failure for me
2) i need to find the sd card location in the twrp file browser (all the folders show empty for me)
if nothing works, i guess i need to wipe my phone, but that's what i would like to avoid. thanks for your help guys!
tempurastyle said:
Yes, after the first upgrade attempt, i let twrp untouched. then when entering twrp, i didnt have a password, so i skipped it. i couldn't find the sd card in the file browser, and after i hit reboot in twrp the phone restarted and got stuck in boot.
So I flashed again, this time deleting twrp. the initial boot up went fine. Then i flashed twrp again and once again, without having a password, i just skipped the password prompt. still couldnt find the sd card, and i rebooted out of twrp. and the phone got stuck again.
after 2-3 trials, i figured out that everytime i rebooted out of twrp, the phone gets stuck during boot. even after turning it off and on, so a reflash was needed.
now i have given up using twrp, so i have an unrooted phone with an unlocked bootloader. which does not allow me to use android pay. i think to solve my problem is:
1) i need to know which twrp version really works, i have tried
this version
and this version
both cause a boot failure for me
2) i need to find the sd card location in the twrp file browser (all the folders show empty for me)
if nothing works, i guess i need to wipe my phone, but that's what i would like to avoid. thanks for your help guys!
Click to expand...
Click to collapse
The 2. issue with the sdcard is easy. After pressing 'install' button in twrp at the bottom left press the "select storage' button, a small window will pop up then select the 'micro sdcard' and press 'ok", you should see your files now.
The 1. ssue is really odd! I use the second twrp you posted, for some wierd reason the first one does not boot for me (twrp does not start). But I talked with another guy for him it was the other way around. It was really strange. I think most can use both though without problems
There is one more twrp 3.1 from bambamx, but I really do not get this, twrp boots from its own partition with its own kernel. They should be separated unless twrp does something to system ofcause which it very well shouldn't unless you ask it to, deleting a important file or flashing something. I have never heard of this sorry. One thing is certain our device sure could use a stable nougat encryption compatible twrp!
I will let you know if I find something, you can try the last available version, I have no idea if it will exhibit the same strange behaviour. But maybe its worth a shot although it seems something else is at play.
A couple of stupid questions sorry; You disabled dm verity and sony ric in ta poc right, and it does not happen if you boot your phone normal a couple of times.
Edit: sorry Mr. Sandman had not left so I did not read properly here from the morning. I will edit my post to actually answer as best as I can lol.
Just to let you know:
1. You do not need to install TWRP to use it! You can just do
Code:
fastboot boot <TWRP image>
to run TWRP on the phone (instead of
Code:
fastboot flash boot <TWRP image>
). The only drawback of this method is that you will always need a computer to enter TWRP. Btw. with this method you can also try out a custom kernel image before flashing it.
2. You do not need write access to /data partition to install Magisk. It was explained in another thread that Magisk can use /cache temporary when access to /data is not available. It will write to /data on first boot instead.
3. While using TWRP you can use adb to transfer files onto the phone, so you don't need to have them ready on the internal storage.
realtuxen said:
The 2. issue with the sdcard is easy. After pressing 'install' button in twrp at the bottom left press the "select storage' button, a small window will pop up then select the 'micro sdcard' and press 'ok", you should see your files now.
Click to expand...
Click to collapse
I did, but the SD card can't be selected, and the size shows as 0kb. I did a workaround though: i formatted a spare sd card and copied magisk on it. it was instantly recognized and selectable.
ypnos42 said:
Just to let you know:
1. You do not need to install TWRP to use it! You can just do
Code:
fastboot boot <TWRP image>
to run TWRP on the phone (instead of
Code:
fastboot flash boot <TWRP image>
). The only drawback of this method is that you will always need a computer to enter TWRP. Btw. with this method you can also try out a custom kernel image before flashing it.
3. While using TWRP you can use adb to transfer files onto the phone, so you don't need to have them ready on the internal storage.
Click to expand...
Click to collapse
GREAT advice! I launched TWRP from ADB and successfully flashed Magisk using ADB sideload. Thanks, my phone is rooted again!
Hey,hey,hey
Did you facing error while installing Full Gapps or Stock Gapps? which says installing gapps error because not enough system partition size.
Yes,i'm facing that bug too,but i have a solution for this issue.That bug can be happen because after flashing any Oreo ROM your system partition become smaller,sure that is not normal.
To fix this you need to "resize" your system partition. I almost resize my system partition using an "Extreme Way!" and if i do that maybe my phone goes bricked. Thanks to god i can found what the problem after try "try and error" method so it can be said,this solution I found because of accident.Ok enough
Ok this the simple method.
1. Download Flashable Busybox by @YashdSaraf https://sourceforge.net/projects/busybox-yds/files/Sep-06-17/Busybox-1.27.2-YDS-UNIVERSAL.zip/download original thread https://forum.xda-developers.com/android/software-hacking/tool-busybox-flashable-archs-t3348543
2. Flash your Oreo Custom ROM
3. Flash the flashable busybox.
4. Go to Wipe option
5. Check "system" partition
6. Press Advance Option > press "Resize" (don't worry,you don't need to reflash the rom)
7. Go to Wipe option again
8. Check "system" partition again
9. Press Advance Option > press "Repair"
10. Then,install the GAPPS ,and you can bit this Oreo with GAPPS berry Jam.
This method work perfectly for me.
This should work on Z00L and Z00T :good:
error 1 when repairing the partition. But it still worked. Thanks
Ichijou Raku said:
2. Flash your Oreo Custom ROM
3. Flash the flashable busybox.
4. Go to Wipe option
5. Check "system" partition
6. Press Advance Option > press "Resize" (don't worry,you don't need to reflash the rom)
7. Go to Wipe option again
8. Check "system" partition again
9. Press Advance Option > press "Repair"
10. Then,install the GAPPS ,and you can bit this Oreo with GAPPS berry Jam.
This method work perfectly for me.
This should work on Z00L and Z00T :good:
Click to expand...
Click to collapse
Hey does I need to do this every time when I installing stock gapps?? Or only for the first time??
mg712702 said:
Hey does I need to do this every time when I installing stock gapps?? Or only for the first time??
Click to expand...
Click to collapse
Same question here.
raiden_1115 said:
Same question here.
Click to expand...
Click to collapse
Bro....I just test it and yes you have to de this everytime when you installing oreo....and I didn't flash the busybox....but I successfully resize it.....then the question is what's for the busybox is??
Doing this every installing oreo is,yes...
I think,cannot resize partition is only happened when upgrading Nougat to Oreo ,because every changing an oreo rom to another oreo rom,I dont have to install busybox again..
Busybox...mmmmm try flashing oreo rom after a nougat one,then resize Partition you will facing an error code on twrp say "resize error blablablabla" (or another,im forget what it say) ,for that,im thinking why i cannot resize the partition,While still in nougat I still can resize partition without any problem..And as you know, busybox contains a number of commands that can run in the terminal, and "resizing command" is contained within the busybox ..
Oh,im not responsible with any error after trying this method,But all this time I have never experienced any errors because this method..
Im still a newbie on android,i dont have a lot experience on android..As I said ,i found this method by trying "try and error" method,trying installing nougat first then oreo,trying installing boot.img first then oreo,and much more attempt..and i still got same error hahaha.. frustrated because cannot installing large gapps..
Then i found this method,just try this method and tell me if you found an error after trying this method..
But I can be sure it will not happen just because resize the partition, because resizing partition here instead of changing the size of partition system becomes bigger,Resize here only returns the size of the corrupted partition system
i got an error when resizing and repairing on my lg v20 h918, I still followed steps and ended up with the error after gapp installation. I am back to a blinking black screen after the lg logo. I think my phone is a lost cause.
So I recently rooted and flashed a custom rom (https://forum.xda-developers.com/yureka/general/rom-bootleggers-rom-v2-1-volte-t3777131) on my device, all was working fine until I realized that I didn't flash gapps. Downloaded gapps tried flashing (on TWRP) it but I got the error "error executing updater binary" . Googled up for a solution and got this:
Step 1:- Go to recovery.
Step 2:- Go to Wipe>>Advanced wipe.
Step 3:- Check data, system, cache & dalvik cache and then swipe to wipe all.
Step 4:- Then go to install zip from SD card and browse the Rom and install it.
Step 5:- Reboot the device
After this, somehow, I lost the rom but had my TWRP recovery still but I was able to flash the rom again using "minimal adb and fastboot". Everything was working fine but I still didn't have gapps and I thought I did something wrong with the steps aforementioned so I took a shot at those steps again. And boom! my device now keeps booting into "FASTBOOT MODE"(can't even go to recovery) and I tried several methods to try and fix and the most frequent "fix" I got for this on Google was to use adb and fastboot and use the command "fastboot oem unlock" but that didn't help either. PLEASE HELP ME OUT. JUST NEED TO GET A RECOVERY (TWRP/CWM) and flash my rom
fastboot -i 0x1ebf erase cache
fastboot -i 0x1ebf erase userdata
Flash twrp 3.2.2
fastboot -i 0x1ebf flash recovery twrp_3.2.2.img
Sent from my AO5510 using Tapatalk
---------- Post added at 06:19 AM ---------- Previous post was at 06:18 AM ----------
brickedmyphone1 said:
So I recently rooted and flashed a custom rom (https://forum.xda-developers.com/yureka/general/rom-bootleggers-rom-v2-1-volte-t3777131) on my device, all was working fine until I realized that I didn't flash gapps. Downloaded gapps tried flashing (on TWRP) it but I got the error "error executing updater binary" . Googled up for a solution and got this:
Step 1:- Go to recovery.
Step 2:- Go to Wipe>>Advanced wipe.
Step 3:- Check data, system, cache & dalvik cache and then swipe to wipe all.
Step 4:- Then go to install zip from SD card and browse the Rom and install it.
Step 5:- Reboot the device
After this, somehow, I lost the rom but had my TWRP recovery still but I was able to flash the rom again using "minimal adb and fastboot". Everything was working fine but I still didn't have gapps and I thought I did something wrong with the steps aforementioned so I took a shot at those steps again. And boom! my device now keeps booting into "FASTBOOT MODE"(can't even go to recovery) and I tried several methods to try and fix and the most frequent "fix" I got for this on Google was to use adb and fastboot and use the command "fastboot oem unlock" but that didn't help either. PLEASE HELP ME OUT. JUST NEED TO GET A RECOVERY (TWRP/CWM) and flash my rom
Click to expand...
Click to collapse
https://dl.twrp.me/tomato/
Sent from my AO5510 using Tapatalk
Thank you very much!! I am so sorry for the late af reply, got a little carried away with some other thing(s). I got the recovery now and I used a micro SD card to flash the rom but the problem now is that I'm getting the error 7 ("Updater process ended with ERROR: 7 Error installing zip file "/external_sd/" followed by filename.zip)
and then it says "Updating partition details... Failed to mount '/cache' (Invalid arguement)
...done"
I do not understand what seems to be the problem....I thought the issue might be with me trying to flash it via the memory card so I tried using the "adb sideload" method which yielded the same results. I have no idea what is to be done now
brickedmyphone1 said:
Thank you very much!! I am so sorry for the late af reply, got a little carried away with some other thing(s). I got the recovery now and I used a micro SD card to flash the rom but the problem now is that I'm getting the error 7 ("Updater process ended with ERROR: 7 Error installing zip file "/external_sd/" followed by filename.zip)
and then it says "Updating partition details... Failed to mount '/cache' (Invalid arguement)
...done"
I do not understand what seems to be the problem....I thought the issue might be with me trying to flash it via the memory card so I tried using the "adb sideload" method which yielded the same results. I have no idea what is to be done now
Click to expand...
Click to collapse
Do factory reset in twrp
Do it twice
Then flash ROM as usual
Sent from my AO5510 using Tapatalk
Rajendran Rasa said:
Do factory reset in twrp
Do it twice
Then flash ROM as usual
Sent from my AO5510 using Tapatalk
Click to expand...
Click to collapse
Thank you very much!!!!! That did it! You da man ) just one last query, I'm about to flash gapps(which was the root of all the problems) and I've downloaded the gapps 64 bit cos yu yureka is ARM with 64 bit cpu architecture right?
Edit: I went ahead and tried flashing it with the 64 bit one and after getting the regular twrp messages I got one as "Insufficient storage space available in system partition. You may want to use a smaller open GApps package or consider removing some apps using gapps-config. See:'/sdcard/open_gapps_log.txt' for complete information"
But right now I did a factory reset(ty again) and there's absolutely nothing in my internal storage. The last passage on twrp looks like this ;
"Error Code: 70
-Unmounting /persist /system
Updater process ended with ERROR: 70
Error installing zip file '/sdcard/open_gapps-arm64-8.1-stock-20180705.zip' "
brickedmyphone1 said:
cos yu yureka is ARM with 64 bit cpu architecture right?
Click to expand...
Click to collapse
Right.:good:
~bump~
Edited the last post with new problems ._.
brickedmyphone1 said:
~bump~
Edited the last post with new problems ._.
Click to expand...
Click to collapse
Internal storage and /system partition are different things.
Either download the Pico Gapps package or increase the /system partition size.
saurav007 said:
Internal storage and /system partition are different things.
Either download the Pico Gapps package or increase the /system partition size.
Click to expand...
Click to collapse
Thank you again!
But pray tell, how do I increase my /system partition size?
brickedmyphone1 said:
Thank you again!
But pray tell, how do I increase my /system partition size?
Click to expand...
Click to collapse
Make sure to read everything and only follow it once you understand everything or you always have a risk of bricking your device. You can also opt for Pico Gapps package if you want where you probably won't have to increase any partition size.
http://forums.yuplaygod.com/threads/39966/
saurav007 said:
Internal storage and /system partition are different things.
Either download the Pico Gapps package or increase the /system partition size.
Click to expand...
Click to collapse
saurav007 said:
Make sure to read everything and only follow it once you understand everything or you always have a risk of bricking your device. You can also opt for Pico Gapps package if you want where you probably won't have to increase any partition size.
http://forums.yuplaygod.com/threads/39966/
Click to expand...
Click to collapse
Thank you once again, I will try the same and revert back.