hi everyone,
i have a couple of questions and i favor i would like to ask from anyone who sees this.
i currently own the sony xperia e4 phone which as of right now , doesnt have any development for it since there is no custom recovery yet.
the problem is that the device doesnt have a stock recovery (and no recovery partition).Secondly it has a non-standard boot.img so mkvendor.sh script doesnt work.i am able to get the info myself (base adress, kernel adress etc.) but i dont have a pc atm so i cant compile it and it doesnt have a
recovery partition so i t cant be flash that way. i read something about flashing xperia recoverues on the fotakernel but im not sure if some modifications are needed to do so.
if anyone with a build enviroment and time would like to compile the recovery themself (i will provide files such as the boardconfig myself)pm me.
any help is much appreciated.
Mod edit:
Thread closed as the cross-dev section is not the place for this
Try asking here
https://forum.xda-developers.com/t/xperia-e4
Related
Hi guys just wanted to ask for help from the expert porters.
I've been porting on my own this past weeks and my first try booted up well.
Tried another and still booted well.
But after sometime when I try porting again, it won't boot anymore.
It would pass the splash screen then after that would be BLACK SCREEN.
I'm just curious why this is happening when I did the same procedure I did with the other roms I ported and got it to boot well.
Hope someone could help me.
THANK YOU!
Please specify, which device's ROM were you porting and was it stock or CM7 based?
If it was CM7 based, I am sure there shouldn't be a problem porting it of you have read the guide correctly (rishabhraj one)
If it is stock based ROM of device other than S5830i, it can't be directly ported and you will have to add features and png manually to your device's framework
you must explain the "port" process you did,
what codes you reconfigured and binaries to get working,
I just copied the app,xbin,framework,font,media,lib,etc, and bin folders from port to base and edit buildprop. that's what I did with my first port and it booted well.. It was MIUI 3.4.5.. but when I'm trying to port the updated version, it won't boot anymore.
Take a log cat first
Hi there xda members! i recently bought this alcatel pop c7 (1gb ram version) and like many others i soft bricked it - boot loop - while trying to install a ported miui, that was not good for my phone. So for 8 almost full days, im trying to recover my phone. Tryed every solution that i found here on xda and also other forums. At some point my phone wasnt even charging itself.
I have to mention that my phone was rooted and i have CWM 5.5.0.4 on it ( thanks to you guyz) . But cwm was of no use, backup restoration was of no use.
Finally found out a solution that created a biger problem for me (maybe this will help other users that have the boot loop issue) From the root request thread alcatel pop c7, i found about Cherry Mobile Fuze custom roms, and genesis did work. My phone boots now, it works fine, connects tot the internet but i have no sim detected, no imei and even mtk droid tools and imei generator didnt help (i think its because of the rom that is dual sim, on a single sim phone).
But as the thread from root request alcatel pop c7 sayd ( page 7 post 52) i had to replace boot img from stock and build.prop. Boot img was easy to find, build.prop not. So i took boot img from stock rom (posted here on xda, but bad scatter files) and build.prop i took from the first ported miui rom that bricked my phne. It boots now but no imei. mtk droid tools and imei generator aren't working, but the tutorials with mobile uncle tools, entering engineer mode and writing some comands there, that i think it may solve my phone, but too bad , my new rom has no engineering mode apk.
So im asking the xda comunity, is my phone done? is it gone? can i do something about it ?
Can i get a stock build.prop (maybe that was the problem)?. In my opinion i have a few options but dont know how to proceed in these cases : flash the stock rom (no good stock rom backup untill now, i have downloaded tons of backups) flash engineer mode to change those imeis (didnt find how to do it) use one touch upgrade to force update my phone to stock (is there any way to fool OTU that my phone has an older version of android or no version at all? are there a thing in build.prop that modified can make my phone seem outdated) and lastly a good build.prop.
Sorry for the long post, i wouldnt ever have bothered xda if i was not desperate (usually i find answers to my questions, but now nothing worked)
and also thank you in advance for reading, posting a comment , anything that can help me in my problem. Maybe the trick with genesis rom can unbrick others people alcatel pop c7 phones, but beware, imei may be gone after that.
help !!!
Can anybody help me please???
Alcatel Pop C7 stock Rom.
DragonfO said:
Can anybody help me please???
Click to expand...
Click to collapse
If your interested in unbricking your phone msg me on Instagram @Shevii_1.
EVGA Tegra Note 7
4.3 jelly Bean
Used the Super Tool to flash drivers and unlock bootloader.
Installed TWRP Recovery
Rooted using SU
Everything is working great, at this point.
Failed to back anything up
Flashed Shaky's custom Kernal and I couldn't get past the tegra note 7 screen. - at this point I probably could have saved it but doing anything other than what happens next.
Flashed 4.4 stock Rom which has to have reset the Recovery and Debugging is now off.
Do not do what I did. Brick. Any ideas? I can still get into bootloader which is unlocked but my computer no longer recognizes it. Pretty much lost hope on this one. Surprise me if you feel inclined.
I've been trying to sideload via externalSD, the stock 4.3 ROM from the "Tegra Note Discoveries" thread. It actually gets halfway though installation then fails for reasons I can't begin to understand. Most likely because it's rooted and I'm flashing a stock rom. If anyone can find a way to flash the stock Kernel and 4.3 rom I would be grateful.
share_needles said:
I've been trying to sideload via externalSD, the stock 4.3 ROM from the "Tegra Note Discoveries" thread. It actually gets halfway though installation then fails for reasons I can't begin to understand. Most likely because it's rooted and I'm flashing a stock rom. If anyone can find a way to flash the stock Kernel and 4.3 rom I would be grateful.
Click to expand...
Click to collapse
In the recovery environment , ..... you are inside the ram disk of, whatever recovery you are running and root status of your system ROM doesnt matter .
Since from the 1st post you have recovered it to the point where you can access the recovery, I think its just matter of getting the correct backup re-installed.
You can request someone with same Branding ( there are 6-7 avent, XOLO etc ) to upload their cwm backup ( minus data, cache ).
Lack of developer / geeky user community is what you get when companies lock their bootloader under disguise of Warranty n stuff.
I havnt been able to gather the courage to play with TN7 like i do with my Nexus7, nexus 4 and Xperia J . ( XJ has some great XDA community btw even after closed BL)
kapil.git said:
In the recovery environment , ..... you are inside the ram disk of, whatever recovery you are running and root status of your system ROM doesnt matter .
Since from the 1st post you have recovered it to the point where you can access the recovery, I think its just matter of getting the correct backup re-installed.
You can request someone with same Branding ( there are 6-7 avent, XOLO etc ) to upload their cwm backup ( minus data, cache ).
Lack of developer / geeky user community is what you get when companies lock their bootloader under disguise of Warranty n stuff.
I havnt been able to gather the courage to play with TN7 like i do with my Nexus7, nexus 4 and Xperia J . ( XJ has some great XDA community btw even after closed BL)
Click to expand...
Click to collapse
Yea I jumped in the deep end without doing enough research. I have rooted and installed custom ROMs on my android phone without issue but I've never messed around with kernals or had to dig myself out of a device stuck in boot-mode. Instead of learning about a device then modding it, I forced a situation where I modded now need to learn how to fix it.
As novice as I am, still working on getting the correct drivers installed to sideload a backup. My computer will not recognize the ADB device in the stock bootloader but when I boot into recovery it does recognize it so there is definitely a driver issue there.
By kapil.git
You can request someone with same Branding ( there are 6-7 avent, XOLO etc ) to upload their cwm backup ( minus data, cache ).
Click to expand...
Click to collapse
I think more like a dozen brands of TN7.
You should at least tell your brand, would make it less mysterious.
Advent has a stock 4.3 install install via APX mode (although you seem to be only able to use it once, then it locks
the nvflash stuff).
I apologize I have the EVGA Tegra Note.
share_needles said:
I apologize I have the EVGA Tegra Note.
Click to expand...
Click to collapse
you are lucky ... this thread has many posts of the same branding EVGA..
Top posts & stickies also have a AIO post about recovering a unlocked BL device.. download and do it OP.
Hi Guys. Tablet is working fine now. I used multiple files from multiple sources to get this going. Here were the commands to get me back to stock. Obviously there was a lot of playing with commands etc that I cut out. I truly believe this device is unbrickable. I was just stuck in a bootloop.
in short, the issue was with the boot after a kernel flash. The TWRP recovery was flashed back to stock.
Got the drives from SDK download because I'm not slick enough to be able to do it myself.
In fastboot, make sure you have the fastboot file in the folder with your boot.img , recovery.img
fastboot boot boot.img ----got me out of the bootloop temporarily without flashing anything unnecessary
fastboot flash boot.img, flashed the boot.img from Vega Note 7 source files that are out there, I recommend every download those now.
fastboot boot TWRP_recover.img -----messing around be led me in a good direction
From there, I installed the below file from XDA User e8hffff
Forum post and links: forum.xda-developers.com/showthread.php?t=2580287
Backupfile name: productionbl_signed_tn7_114gp_2923379__4.3.zip
I believe that was a full backup of a 4.3 Evga Tegra Note 7 stock. This really helped me out a lot.
Thanks everyone for the help. You can see by the very few command that got this device up and running I am a total noob but I'm figuring it out little by little.
If anyone is in a similar circumstance in the future send me a PM and I may be able to assist you.
I'm trying to build a twrp recovery...I can get a full build...I just have a few questions...am I building a boot image or recovery image...and basically overall help on the boardconfig.mk file...please any help would be so very much appreciated
I have absolutely 0 experience in the building world, but I also have the 337a if you need any testing or need anything pulled from mine or any testing. Just let me know. You're actually the only other person I've come across with the 337a. ?
I believe there are a few recovery guides here on xda, I'd link to them but I'm on mobile.
I believe what you want to create is a recovery image.
I know I want to make a recovery but on those guides it says that the recovery on a typical samsung device is located in the boot partition on a sepereate ram-disk
dazemc said:
I know I want to make a recovery but on those guides it says that the recovery on a typical samsung device is located in the boot partition on a sepereate ram-disk
Click to expand...
Click to collapse
I can add you to the hangout that I've got with my buddies who are builders. They can help you move forward. PM me your Gmail to add you.
I'm going to try some more here today...I haven't had time
Galaxy 4 tabs have one recovery and one boot partition.
Can someone suggest another forum where I can go for help?
The last 5 or 6 times I've posted questions here, I've gotten no answers at all. I really need help. My tablet was bricked because I lost ADB connection while updating the system partition. I know there is a way around this - I have a custom recovery and an unlocked bootloader - but I need help from someone who knows more than I do. No one here is going to help me, I know. Where do I go? Where can I find someone knowledgeable and helpful?
permutations said:
Can someone suggest another forum where I can go for help?
The last 5 or 6 times I've posted questions here, I've gotten no answers at all. I really need help. My tablet was bricked because I lost ADB connection while updating the system partition. I know there is a way around this - I have a custom recovery and an unlocked bootloader - but I need help from someone who knows more than I do. No one here is going to help me, I know. Where do I go? Where can I find someone knowledgeable and helpful?
Click to expand...
Click to collapse
Have you tried booting to recovery from bootloader and regaining an ADB connection? This should be all you need.
permutations said:
Can someone suggest another forum where I can go for help?
The last 5 or 6 times I've posted questions here, I've gotten no answers at all. I really need help. My tablet was bricked because I lost ADB connection while updating the system partition. I know there is a way around this - I have a custom recovery and an unlocked bootloader - but I need help from someone who knows more than I do. No one here is going to help me, I know. Where do I go? Where can I find someone knowledgeable and helpful?
Click to expand...
Click to collapse
The more information you provide, the better. Please provide more information regarding your device so that your thread can be placed in the correct forum.
Magnum_Enforcer said:
The more information you provide, the better. Please provide more information regarding your device so that your thread can be placed in the correct forum.
Click to expand...
Click to collapse
I was updating my Nexus 10 tablet - had gotten to the system partition - when I lost the ADB connection. I've since learned that's a problem with newer Macs (I was connected to Windows through Parallels). Here's a link to a thread about that:
https://code.google.com/p/android/i...Stars Reporter Opened&groupby=&sort=&id=65301
Because of the lost connection, the system partition did not flash and my tablet is bricked. There is no operating system so it can't boot into Android, but it can boot into the Bootloader and Recovery mode. All the other partitions are fine.
I have a custom recovery (TWRP) and an unlocked bootloader, but I'm at a loss to figure out how to flash the system.img file. I can't boot to Android so I can't connect through ADB in Fastboot mode to flash the ordinary way. I am connected through ADB when I'm in Recovery mode, but I can't use the flash command in Recovery mode. Nor can I figure out a way to make TWRP flash the partition by running it as a zip file - mainly because I can't figure out what the update.zip file should consist of. There was an OTA update file on my device when I started the manual update (manual updates fail), but I didn't look at it and didn't save it.
I tried pushing the system.img file to the Nexus 10 using the Linux dd command, but that doesn't work with the system partition, which uses a special format. The details are explained here, but I don't fully understand it:
http://www.modaco.com/forums/topic/327661-how-to-backup-the-systemimg-bootimg-and-recoveryimg/
After spending about 8 hours on this last night, I believe the only way I can fix it is to create an update.zip file that uses a Linux script to flash the system partition, but this is way beyond my skill set and I can't find a model for how to do this anywhere. All tutorials I've found for creating zip files for flashing are for installing apps, not flashing a system partition - which is even more complicated than flashing, say, a boot partition. Nor can I find an update.zip file from someone's cache (sure wish I'd saved mine) to use as a model. I'm looking for someone with this kind of high level knowledge who can give me guidance - or someone who can refer me to someone who has this kind of knowledge.
I solved this problem.